From: Neil Jerram <neil@ossau.uklinux.net>
To: alto_stan@wanadoo.be
Cc: Marius Vollmer <mvo@zagadka.ping.de>,
guile-gtk@sources.redhat.com, guile-user@gnu.org
Subject: Re: general debugging question
Date: Thu, 28 Nov 2002 02:32:00 -0000 [thread overview]
Message-ID: <m31y56t5ta.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <20021128093703.1fe573c2.alto_stan@wanadoo.be>
>>>>> "Stan" == Stan Pinte <alto_stan@wanadoo.be> writes:
Stan> It is segfaulting somewhere...
Stan> Is my only solution putting
Stan> (format #f ...) in all my code, until I spot the place, or is there a
Stan> guilish solution to that problem? (like printing the stack, or
Stan> printing each call to a function?)
If you know what the top level call is, say `foo-bar', and you are
using unstable CVS, the following _might_ successfully tell you the
last Scheme thing that happened before the segv:
guile> (use-modules (ice-9 debugger breakpoints))
guile> (use-modules (ice-9 debugger breakpoints procedural))
guile> (trace-subtree! foo-bar)
guile> (foo-bar)
Stan> or shall I use gdb? (and if yes, has anyone done that already?)
It would be nice if one could ask for a Scheme backtrace from GDB; I
don't think this is possible today. (Maybe try `call
scm_backtrace()'.)
Neil
next prev parent reply other threads:[~2002-11-28 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 0:01 compilation problem in guile-gtk CVS Stan Pinte
2002-11-22 12:44 ` Marius Vollmer
2002-11-28 0:18 ` general debugging question Stan Pinte
2002-11-28 2:32 ` Neil Jerram [this message]
2002-11-28 9:23 ` general debugging question + Segfault in guile-gtk Stan Pinte
2002-11-28 14:37 ` Daniel Skarda
2002-11-28 23:53 ` Stan Pinte
2002-11-28 23:53 ` guile-gtk-1.2 CVS % gtk-pixmap-new Stan Pinte
2002-11-29 11:56 ` Daniel Skarda
2002-12-01 2:48 ` Stan Pinte
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m31y56t5ta.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=alto_stan@wanadoo.be \
--cc=guile-gtk@sources.redhat.com \
--cc=guile-user@gnu.org \
--cc=mvo@zagadka.ping.de \
/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).