From: Brian S McQueen <bqueen@nas.nasa.gov>
Subject: debugging
Date: Tue, 13 Apr 2004 09:20:08 -0700 (PDT) [thread overview]
Message-ID: <Pine.GSO.4.58.0404130919390.21948@marcy.nas.nasa.gov> (raw)
I have been using guile to handle the logic of a project (also to make the
project fun). Anyway, I needed to do a bit of debugging yesterday, and I
decided to finally try to figure out the guile debugging tools. I think I
found the right stuff, but I am puzzled by the results. Near the top of
my guile script I put:
(debug-enable 'backtrace)
(debug-enable 'debug)
(debug-enable 'trace)
This seemed to do nothing. What am I missing?
I was hoping for a stack dump or syntax error reporting. For some reason
I get no diagnostic information at all from my embedded scheme
interpreter, but the command line guile has plenty of diagnostic
information. How do I get this diagnostic information into my embedded
interpreter?
Brian McQueen
NAS Division
NASA/Ames
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2004-04-13 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 16:20 Brian S McQueen [this message]
2004-04-14 14:04 ` debugging Linas Vepstas
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=Pine.GSO.4.58.0404130919390.21948@marcy.nas.nasa.gov \
--to=bqueen@nas.nasa.gov \
/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).