Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <thiago.bauermann@gmail.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@redhat.com>,  Reid Kleckner <rnk@mit.edu>,
	 unladen-swallow@googlegroups.com
Subject: Re: [RFA] Add interface for registering JITed code
Date: Fri, 31 Jul 2009 18:18:00 -0000	[thread overview]
Message-ID: <200907311201.28986.thiago.bauermann@gmail.com> (raw)
In-Reply-To: <200907301501.17812.thiago.bauermann@gmail.com>

Ok, I had one night's sleep over this, and just re-read the thread. :-)

Em Quinta-feira 30 Julho 2009 15:01:17 Thiago Jung Bauermann escreveu:
> Em Quinta-feira 30 Julho 2009 12:12:50 Tom Tromey escreveu:
> > >>>>> "Reid" == Reid Kleckner <rnk@mit.edu> writes:
> >
> > Tom> Yeah.  This would work if you had two JITs in a process, say loaded
> > Tom> dynamically, and the various __jit symbols had hidden visibility.
> >
> > Reid> I think if someone has that use case, then they can write a client
> > Reid> side library that wraps the __jit symbols and make the two JITs
> > call Reid> that.
> >
> > Yeah, I changed my mind, let's not worry about it.  If it ever comes up,
> > we can deal with it then without breaking compatibility.
>
> If/when someone wants to add another scripting language to GDB, we will be
> bitten by this issue. I can see that happening already. :-)

I still think this will happen soon enough ...

> You're saying that the current patch is extensible to deal with that?

... but I agree with Reid in that the inferior (or client) can deal with that 
case internally (also it seems fair, since it is the client who wanted to have 
two JITs in the first place. :-) ). It is nice that the GDB-facing interface is 
as simple as possible.

Also the protocol is versioned. That is awesome. I don't have worries 
regarding this issue.

> Also, changing subjects: it is important that this feature works on core
> files, or at least is forward-compatible with such a feature. I think this
> needs to be thought through before the patch goes in.

I still think that the patch needs to be tested with a core file scenario 
before it is checked in. Since said scenario is similar to attaching to a 
running process, it will likely magically work, though.
-- 
[]'s
Thiago Jung Bauermann


  reply	other threads:[~2009-07-31 15:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23  1:58 Reid Kleckner
2009-07-23 12:08 ` Reid Kleckner
2009-07-23 23:21 ` Tom Tromey
2009-07-24 13:25   ` Ulrich Weigand
2009-07-24 16:52     ` Doug Evans
2009-07-25  0:40     ` [unladen-swallow] " Reid Kleckner
2009-07-24 16:55   ` Reid Kleckner
2009-07-24 20:42     ` Eli Zaretskii
2009-07-24 20:55       ` Tom Tromey
2009-07-25 15:29         ` Eli Zaretskii
2009-07-27 23:20           ` Reid Kleckner
2009-07-28 20:20             ` Eli Zaretskii
2009-07-28 22:23               ` Reid Kleckner
2009-07-29 15:20                 ` Eli Zaretskii
2009-07-24 21:06     ` Tom Tromey
2009-07-25  0:23       ` Reid Kleckner
2009-07-30 16:30         ` Tom Tromey
2009-07-30 16:54           ` Tom Tromey
2009-08-05 21:05             ` [unladen-swallow] " Reid Kleckner
2009-07-30 21:10           ` Thiago Jung Bauermann
2009-07-31 18:18             ` Thiago Jung Bauermann [this message]
2009-07-31 20:31               ` [unladen-swallow] " Reid Kleckner
2009-08-01 14:43                 ` Thiago Jung Bauermann
2009-08-14 19:29                 ` Tom Tromey
2009-08-14 23:37                   ` Reid Kleckner
2009-08-17 15:31                     ` Tom Tromey
2009-08-20 18:22                       ` Doug Evans
2009-08-21 15:17                         ` Ken Werner
2009-08-21 16:31                           ` Doug Evans
2009-08-21 18:59                             ` Ken Werner
2009-08-21 19:53                               ` Doug Evans
2009-07-31 20:55               ` Paul Pluzhnikov

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=200907311201.28986.thiago.bauermann@gmail.com \
    --to=thiago.bauermann@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=rnk@mit.edu \
    --cc=tromey@redhat.com \
    --cc=unladen-swallow@googlegroups.com \
    /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