From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user@gnu.org
Subject: Re: Need help finding heap corruption bug
Date: Sat, 23 Sep 2006 12:18:25 +0100 [thread overview]
Message-ID: <87fyeikf0e.fsf@ossau.uklinux.net> (raw)
In-Reply-To: ca8589e00609171113t4fb22138ue54bf956d5feb8a7@mail.gmail.com
"Pat Lasswell" <imofftoseethewizard@gmail.com> writes:
> I have two questions. Is there something intrinsically wrong with with setting
> the current module to the one on which I am actively working and then just
> reloading that file rather than the entire suite?
No.
>
> My second question is this: given that the answer to 1) is no, how do I track
> this pest down?
Based on the other messages in this thread, it doesn't sound like
there's an obvious overall problem with Guile on MacOS. It may still
be MacOS-specific, though. Do you know whether the same steps cause
problems on Linux?
> Placing an undefined identifier, say 'x', at various points in
> one of the modules will sometimes produce the appropriate warning, sometimes
> produce a segfault, other times a bus error or illegal instruction or even an
> abort during gc. I have run attached to gdb, but I get a deep stack (131
> frames) ending with, e.g.
>
> #0 scm_gc_sweep () at ../../../src/guile-1.6.8/libguile/gc.c:1729
> #1 0x0021f573 in scm_igc (what=0x26c720 "cells") at ../../../src/guile-1.6.8/
> libguile/gc.c:1161
> #2 0x0021fa83 in scm_gc_for_newcell (master=0x273440, freelist=0x273438) at ..
> /../../src/guile- 1.6.8/libguile/gc.c:985
> #3 0x00238aef in scm_cons (x=0x6826c0, y=0x2974) at ../../../src/guile-1.6.8/
> libguile/pairs.c:84
> #4 0x00216b87 in scm_deval (x=0xc3028, env=0x682480) at ../../../src/
> guile-1.6.8/libguile/eval.c:2835
> #5 0x00219af5 in scm_deval (x=0xc3030, env=0x682480) at ../../../src/
> guile-1.6.8/libguile/eval.c:2819
>
> Are there guile primitives to verify the heap?
Apart from (gc), no. :-)
The only approach I can think of right now is to look at the detail of
why scm_gc_sweep is aborting and work back from there. Anyone have
any other ideas?
Regards,
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-09-23 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 18:13 Need help finding heap corruption bug Pat Lasswell
2006-09-18 8:27 ` Ludovic Courtès
2006-09-18 14:24 ` Pat Lasswell
2006-09-18 15:08 ` Ludovic Courtès
2006-09-18 15:08 ` Pat Lasswell
2006-09-18 23:57 ` Kevin Ryde
2006-09-23 11:18 ` Neil Jerram [this message]
[not found] ` <ca8589e00609231109j36f07390i8fe88c8d0e396079@mail.gmail.com>
2006-09-23 18:10 ` Pat Lasswell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fyeikf0e.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).