From: Eli Zaretskii <eliz@gnu.org>
To: Gary Benson <gbenson@redhat.com>
Cc: gdb-patches@sourceware.org, mark@klomp.org,
jan.kratochvil@redhat.com, dje@google.com
Subject: Re: [RFA take 5] Allow setting breakpoints on inline functions (PR 10738)
Date: Mon, 20 Feb 2012 19:24:00 -0000 [thread overview]
Message-ID: <83wr7htosv.fsf@gnu.org> (raw)
In-Reply-To: <20120220155848.GA5813@redhat.com>
> Date: Mon, 20 Feb 2012 15:58:49 +0000
> From: Gary Benson <gbenson@redhat.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, Mark Wielaard <mark@klomp.org>,
> Jan Kratochvil <jan.kratochvil@redhat.com>,
> Doug Evans <dje@google.com>
>
> This patch makes GDB able to set breakpoints on inlined functions.
Thanks.
> I have updated the documentation part of the patch to retain all
> information about older versions, and also to document the new
> option.
>
> How does it look?
Looks good, but I have a couple of minor comments.
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -44,6 +44,8 @@
> * The command "info catch" has been removed. It has been disabled
> since December 2007.
>
> +* GDB can now set breakpoints on inlined functions.
> +
I think we should also advertise the new command-line option in NEWS.
> +@item -allow-incomplete-gdb-indexes
> +@cindex @code{--allow-incomplete-gdb-indexes}
> +This option causes @value{GDBN} to read and use possibly incomplete
> +@samp{.gdb_index} sections in symbol files. This can speed up
> +startup, but may result in some functionality being lost.
Please add here a cross-reference to the node "Index Section Format",
because the effect of this option is not fully understood until the
reader reads there.
The documentation parts are OK, with those comments taken care of.
next prev parent reply other threads:[~2012-02-20 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 16:16 Gary Benson
2012-02-20 19:24 ` Eli Zaretskii [this message]
2012-02-20 20:26 ` Jan Kratochvil
2012-02-22 14:58 ` Jan Kratochvil
2012-02-22 17:20 ` Doug Evans
2012-02-23 11:15 ` Jan Kratochvil
2012-02-23 11:18 ` Gary Benson
[not found] ` <CADPb22Qi8=Z_Q7j60dPP010eXdjPq2yiftT0x43dF=zmL8H64Q@mail.gmail.com>
2012-02-20 20:42 ` 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=83wr7htosv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark@klomp.org \
/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