Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@sebabeach.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org, gdb-patches@sourceware.org
Subject: Re: guile scripting for gdb
Date: Sun, 10 Nov 2013 06:26:00 -0000	[thread overview]
Message-ID: <CAA8o+=QQB4yUSQVxxxDqzKLYVhDkAM-V-qjp9HjDjqgPh1BubA@mail.gmail.com> (raw)
In-Reply-To: <CAA8o+=Qhwj720CtfhUF=JuLs-GJ455uZ7gsRRripc=4vZDFWng@mail.gmail.com>

On Sat, Nov 9, 2013 at 10:40 AM, Doug Evans <dje@sebabeach.org> wrote:
>> As discussed on IRC, one possible issue is eq?-ness of SMOBs: one would
>> usually expects pointer equality to be preserved at the Scheme level.
>
> Yeah.
> That'll require gdb maintaining its own table(s) for each kind of smob
> we want to intern.

Actually, to be more precise, it will require maintaining tables for
*some* smobs we want to intern.
For other smobs the cost of caching the SCM in the gdb object isn't onerous.
[The object is marked as protected from GC until the gdb object is deleted.]

Alas, for two of the more important smobs we'd want to eq?, I think,
gdb symbols and types, we'll need separate tables.
Minimizing space usage of their gdb structs is important (critical
even), and only a small fraction of them will typically be used in
Scheme.
And we certainly don't want to pay that expense when Scheme isn't used.


  parent reply	other threads:[~2013-11-09 20:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 16:04 Doug Evans
     [not found] ` <87ob5vlr2s.fsf@gnu.org>
2013-11-09 19:47   ` Doug Evans
2013-11-09 19:48     ` Thien-Thi Nguyen
2013-11-10  6:26     ` Doug Evans [this message]
2013-11-11  1:50     ` Ludovic Courtès
2013-11-11  6:28       ` Doug Evans
2013-11-11  6:37         ` Doug Evans
2013-11-11 13:16           ` Ludovic Courtès
2013-11-11 11:55         ` Ludovic Courtès

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='CAA8o+=QQB4yUSQVxxxDqzKLYVhDkAM-V-qjp9HjDjqgPh1BubA@mail.gmail.com' \
    --to=dje@sebabeach.org \
    --cc=gdb-patches@sourceware.org \
    --cc=guile-user@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