Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Reid Kleckner <rnk@mit.edu>
Cc: tromey@redhat.com, gdb-patches@sourceware.org,
	unladen-swallow@googlegroups.com
Subject: Re: [RFA] Add interface for registering JITed code
Date: Fri, 24 Jul 2009 20:42:00 -0000	[thread overview]
Message-ID: <83iqhh52un.fsf@gnu.org> (raw)
In-Reply-To: <9a9942200907240946q1546646ft6e9112f263bcefdf@mail.gmail.com>

> From: Reid Kleckner <rnk@mit.edu>
> Date: Fri, 24 Jul 2009 09:46:52 -0700
> Cc: gdb-patches@sourceware.org, unladen-swallow@googlegroups.com
> 
> > Given that this will be a supported way for GDB to connect to JITs, I
> > think that the official interface (symbol names, types, enum values,
> > etc) should be documented in the GDB manual somewhere.
> 
> Where should this go?  It doesn't really fit under any of the
> top-level topics, so far as I can tell.

Sorry to chime in this late (patches posted as binary attachments
usually discourage me from looking at them), but I cannot answer the
question at this time, given what I know about this feature.  Maybe if
you post what you think should be described in the manual, I can make
up my mind then.

> > This patch also deserves an entry in NEWS.
> 
> Done.

Unfortunately, the NEWS entry is not instrumental enough.  It doesn't
tell the user how to use the feature.  Is it possible to come up with
a more useful entry?


  reply	other threads:[~2009-07-24 18:54 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 [this message]
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
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=83iqhh52un.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