Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sanjoy Das <sanjoy@playingwithpointers.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 7/7] Add documentation.
Date: Tue, 09 Aug 2011 15:51:00 -0000	[thread overview]
Message-ID: <83ei0uzipf.fsf@gnu.org> (raw)
In-Reply-To: <1312903509-25132-8-git-send-email-sanjoy@playingwithpointers.com>

> From: Sanjoy Das <sanjoy@playingwithpointers.com>
> Cc: Sanjoy Das <sanjoy@playingwithpointers.com>
> Date: Tue,  9 Aug 2011 20:55:09 +0530
> 
> +@node Custom Debug Info
> +@section Custom Debug Info

Please add a couple of @cindex entries here for the subjects of this
section.

> +A mentioned

Probably meant "as mentioned" here.

>                readers can be loaded using the @code{load-jit-reader}
> +command.  Executing @code{load-jit-reader foo} will have @value{GDBN}
> +try to load @code{foo.so}

@file{foo.so}

Btw, is the .so extension hard-coded?  That is, does this feature
support only Posix-style shared libraries, or Windows-style as well?

> from @code{$libdir/gdb} where @code{libdir}

@file{@var{libdir}/gdb}

"libdir" is a place-holder, so it should be in @var.

> +is the library directory for the system (usually something like
> +@code{/usr/local/lib}).

@file{/usr/local/lib}

> +further interaction is required from the user's side.  The current
> +reader can be unloaded by executing @code{unload-jit-reader},

Please describe the commands in the format we use for all the other
commands, including @kindex entries etc.

>                                                              after
> +which a new reader may be loaded, using @code{load-jit-reader} as
> +usual.

Does this mean only one reader can be loaded at any given time?  If
so, this should be said explicitly.  What happens if I try to load
another one without unloading first?

> +As mentioned, a reader is essentially a shared object conforming to a
> +certain ABI.  This ABI is described in @file{jit-reader.h}.

jit-reader.h or jit-reader.h.in?  The previous section used the
latter.

> +@value{GDBN}), in @code{$includedir/gdb} where @code{$includedir} is
> +the system include directory.

@file{@var{includedir}/gdb} and @var{includedir}

> +Readers need to be released under a GPL compatible license.  A reader
> +can be declared released under such a license by placing the macro
          ^^^^^^^^^^^^^^^^^
"declared as released", probably.

> +those object files. @code{struct gdb_unwind_callbacks} has callbacks
                     ^^
Need two spaces here.

> +to read registers off the current frame and to write out the values of
> +the registers in the previous frame. Both have a callback
                                      ^^
Likewise.

Thanks.


      reply	other threads:[~2011-08-09 15:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 15:21 [PATCH] JIT debug info Reader Sanjoy Das
2011-08-09 15:21 ` [PATCH 3/7] New commands for loading and unloading a reader Sanjoy Das
2011-08-12 20:58   ` Tom Tromey
2011-08-09 15:21 ` [PATCH 4/7] Use the loaded reader Sanjoy Das
2011-08-15 20:21   ` Tom Tromey
2011-08-09 15:21 ` [PATCH 1/7] Introduce header (jit-reader.h.in) and modify build system Sanjoy Das
2011-08-09 15:40   ` Eli Zaretskii
2011-08-09 15:43     ` Sanjoy Das
2011-08-09 15:53       ` Eli Zaretskii
2011-08-20 17:17     ` Jan Kratochvil
2011-08-20 17:31       ` Eli Zaretskii
2011-08-20 17:42         ` Jan Kratochvil
2011-08-20 17:52           ` Eli Zaretskii
2011-08-10 20:57   ` Tom Tromey
2011-08-09 15:21 ` [PATCH 2/7] Add platform agnostic dynamic loading code Sanjoy Das
2011-08-10 21:01   ` Tom Tromey
2011-08-09 15:21 ` [PATCH 6/7] Register the proxy unwinder Sanjoy Das
2011-08-12 21:07   ` Tom Tromey
2011-08-09 15:21 ` [PATCH 5/7] Add a " Sanjoy Das
2011-08-15 20:38   ` Tom Tromey
2011-08-20  6:26     ` Sanjoy Das
2011-08-09 15:21 ` [PATCH 7/7] Add documentation Sanjoy Das
2011-08-09 15:51   ` Eli Zaretskii [this message]

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=83ei0uzipf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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