unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
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: Fri, 26 Jun 2009 22:33:06 +0100	[thread overview]
Message-ID: <87vdmik7e5.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <86bpobzb3x.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri\, 26 Jun 2009 09\:51\:30 +0200")

ludo@gnu.org (Ludovic Courtès) writes:

> Hi Neil,

Hi Ludo!

> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> Wow, that's pretty cool!  So your patches are actually in GDB now, are
>> they?
>
> Yes, but as I said, they're not too useful as it stands.

I don't really understand why you say that.  They look useful to me.

>> 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?
>
> I think so.

Thanks.

>> (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?)
>
> Currently, it just calls `gdb_print ()' et al. in the inferior process.
> Eventually, it should use its own printers, so that it can work without
> interfering the process being debugged, work on core files, etc.

Ah yes, of course, GDB must be able to do that...

Regards,
        Neil




  reply	other threads:[~2009-06-26 21:33 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
2009-06-26  7:51     ` Ludovic Courtès
2009-06-26 21:33       ` Neil Jerram [this message]
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=87vdmik7e5.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).