From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Guile and GDB
Date: Thu, 25 Jun 2009 23:59:20 +0100 [thread overview]
Message-ID: <87tz23udh3.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <8663ek2ayd.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri\, 26 Jun 2009 00\:41\:14 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> 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 .
Wow, that's pretty cool! So your patches are actually in GDB now, are
they?
Notwithstanding, it looks like my conclusion that we don't need
GDB_INTERFACE and GDB_INTERFACE_INIT in guile.c is still correct - can
you confirm that?
(In other words, instead of using some kind of registration API, I
guess that GDB either links to libguile, or looks up the gdb_*
functions that it needs dynamically, or has an independent copy of the
libguile code that it needs to do printing. Is that right?)
Regards,
Neil
next prev parent reply other threads:[~2009-06-25 22:59 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 ` Guile and GDB Ludovic Courtès
2009-06-25 22:59 ` Neil Jerram [this message]
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=87tz23udh3.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=ludo@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).