Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Sanjoy Das <sanjoy@playingwithpointers.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 7/7] Documentation.
Date: Tue, 30 Aug 2011 19:43:00 -0000	[thread overview]
Message-ID: <m3k49uadnz.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1314518609-10204-8-git-send-email-sanjoy@playingwithpointers.com>	(Sanjoy Das's message of "Sun, 28 Aug 2011 13:33:29 +0530")

>>>>> "Sanjoy" == Sanjoy Das <sanjoy@playingwithpointers.com> writes:

Sanjoy> Add some basic documentation to gdb.texinfo about the new JIT reader
Sanjoy> functionality. Most of the actual documentation is still in
Sanjoy> jit-reader.h.

I think Eli already approved the docs; so no need to repost in that
situation.

However...

Sanjoy> +The reader is implemented as a shared object.  Two new @value{GDBN}
Sanjoy> +commands, @code{load-jit-reader} and @code{unload-jit-reader} are

The commands are actually jit-reader-load and jit-reader-unload.
This affects a good chunk of the patch.

Tom


  reply	other threads:[~2011-08-30 19:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-27 13:08 JIT Debug Info Reader Sanjoy Das
2011-08-27 13:08 ` [PATCH 4/7] New commands for loading and unloading a reader Sanjoy Das
2011-08-27 14:51   ` Abhijit Halder
2011-08-27 13:08 ` [PATCH 6/7] New JIT unwinder Sanjoy Das
2011-08-28  2:17   ` Sergio Durigan Junior
     [not found]   ` <1314518609-10204-1-git-send-email-sanjoy@playingwithpointers.com>
2011-08-28  8:04     ` [PATCH 5/7] Use the loaded reader Sanjoy Das
2011-08-30 19:18       ` Tom Tromey
2011-08-28  8:04     ` [PATCH 7/7] Documentation Sanjoy Das
2011-08-30 19:43       ` Tom Tromey [this message]
2011-08-28  8:04     ` [PATCH 6/7] New JIT unwinder Sanjoy Das
2011-08-30 19:28       ` Tom Tromey
2011-08-28  8:04     ` [PATCH 3/7] Platform agnostic dynamic loading code Sanjoy Das
2011-08-28  8:04     ` [PATCH 4/7] New commands for loading and unloading a reader Sanjoy Das
2011-08-30 18:52       ` Tom Tromey
2011-08-28  8:05     ` [PATCH 2/7] Relocatable directory for loading JIT readers Sanjoy Das
2011-08-30 18:32       ` Tom Tromey
2011-08-28  8:07     ` [PATCH 1/7] Introduce jit-reader.in and modify build system Sanjoy Das
2011-08-30 18:30       ` Tom Tromey
2011-08-31  3:16         ` Sanjoy Das
2011-08-31 17:44           ` Tom Tromey
2011-08-27 13:08 ` [PATCH 3/7] Platform agnostic dynamic loading code Sanjoy Das
2011-08-27 13:08 ` [PATCH 2/7] Relocatable directory for loading JIT readers Sanjoy Das
2011-08-27 13:08 ` [PATCH 5/7] Use the loaded reader Sanjoy Das
2011-08-27 13:47   ` Abhijit Halder
2011-08-27 14:18     ` Abhijit Halder
2011-08-27 13:08 ` [PATCH 1/7] Introduce jit-reader.in and modify build system Sanjoy Das
2011-08-27 13:08 ` [PATCH 7/7] Documentation Sanjoy Das
  -- strict thread matches above, loose matches on Subject: below --
2011-08-31  3:31 JIT Reader (re-roll) Sanjoy Das
2011-08-31  3:32 ` [PATCH 7/7] Documentation Sanjoy Das
2011-08-24 18:57 JIT Debug Info Reader (re-roll) Sanjoy Das
2011-08-24 18:57 ` [PATCH 7/7] Documentation Sanjoy Das
2011-08-24 20:14   ` Eli Zaretskii

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=m3k49uadnz.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sanjoy@playingwithpointers.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