Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: rnk@mit.edu, gdb-patches@sourceware.org,
	unladen-swallow@googlegroups.com
Subject: Re: [RFA] Add interface for registering JITed code
Date: Sat, 25 Jul 2009 15:29:00 -0000	[thread overview]
Message-ID: <83eis5440j.fsf@gnu.org> (raw)
In-Reply-To: <m3hbx1q48p.fsf@fleche.redhat.com>

> Cc: Reid Kleckner <rnk@mit.edu>, gdb-patches@sourceware.org,
>         unladen-swallow@googlegroups.com
> From: Tom Tromey <tromey@redhat.com>
> Date: Fri, 24 Jul 2009 13:18:30 -0600
> 
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> Eli> Unfortunately, the NEWS entry is not instrumental enough.  It doesn't
> Eli> tell the user how to use the feature.  Is it possible to come up with
> Eli> a more useful entry?
> 
> I think the NEWS entry is fine.  The feature works automatically.  Users
> need do nothing.

Maybe that is true, but the text as written left me wondering whether
I do need to do something to get that working.

    +* GDB now has an interface for JIT compilation.  Applications that
    +dynamically generate code can create object files with debug info in
    +memory and register them with GDB.  The interface also supports
    +attaching to a running process.

The second sentence begs 2 questions: (1) how does one write or
compile or otherwise get hold of such applications, and (2) how does
one register object files with GDB.

Granted, a NEWS entry is not a place for long explanations (if they
are long), but without any pointers to the manual or at least some Web
site, I couldn't figure out how to go about adding this feature to my
workflow.


  reply	other threads:[~2009-07-25  7:27 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 [this message]
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
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=83eis5440j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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