From: ludo@gnu.org (Ludovic Courtès)
To: "Neil Jerram" <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Guile and GDB
Date: Fri, 26 Jun 2009 00:41:14 +0200 [thread overview]
Message-ID: <8663ek2ayd.fsf@gnu.org> (raw)
In-Reply-To: <E1MJvkU-0000SB-UB@cvs.savannah.gnu.org> (Neil Jerram's message of "Thu, 25 Jun 2009 20:40:47 +0000")
Hello,
"Neil Jerram" <neil@ossau.uklinux.net> writes:
> The first kind is that libguile includes the utility functions
> gdb_print, gdb_eval, etc., and the variable gdb_output. These have no
> purpose except for developers to use from GDB when debugging
> something. For example, if you have a SCM x and want to know what it
> is, you can do:
>
> (gdb) call gdb_print(x)
> (gdb) p gdb_output
Actually, it's also meant to be used directly by GDB. Normally, GDB
should try to display SCM values on its own (using its own copy of
`tags.h' and the corresponding printing procedures) and resort to
calling `gdb_print ()' when it doesn't know how to display a value.
In practice, GDB currently only supports the latter, which makes it
not-so-useful (the same result can be achieved with trivial GDB macros).
See http://sourceware.org/ml/gdb-patches/2007-07/msg00231.html .
Thanks,
Ludo'.
next parent reply other threads:[~2009-06-25 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1MJvkU-0000SB-UB@cvs.savannah.gnu.org>
2009-06-25 22:41 ` Ludovic Courtès [this message]
2009-06-25 22:59 ` Guile and GDB Neil Jerram
2009-06-26 7:51 ` Ludovic Courtès
2009-06-26 21:33 ` Neil Jerram
2009-06-26 22:09 ` Ludovic Courtès
2009-06-27 9:34 ` Neil Jerram
2009-06-27 23:22 ` Ludovic Courtès
2009-06-28 9:27 ` Neil Jerram
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=8663ek2ayd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).