From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>,
Eli Zaretskii <eliz@gnu.org>, Pedro Alves <palves@redhat.com>,
dje@google.com, gdb-patches@sourceware.org, mark@klomp.org
Subject: Re: [RFA take 6] Allow setting breakpoints on inline functions (PR 10738)
Date: Thu, 15 Mar 2012 19:34:00 -0000 [thread overview]
Message-ID: <CADPb22Rq4kDOJKWpX94dk_0N2g+EAc44UTCZynZSGpdujkfxmg@mail.gmail.com> (raw)
In-Reply-To: <20120315192931.GA11584@redhat.com>
On Thu, Mar 15, 2012 at 12:29 PM, Gary Benson <gbenson@redhat.com> wrote:
> Jan Kratochvil wrote:
>> On Thu, 15 Mar 2012 19:36:24 +0100, Eli Zaretskii wrote:
>> > Do not reject obsolete .gdb_index sections with possibly
>> > inaccurate info.
>> >
>> > However, if everyone else is tired of bikeshedding, go ahead with
>> > whatever you like.
>>
>> I would like make clear from the option help that it will have
>> negative effect on GDB functionality; that it is not just some
>> performance tuning. So leaving the right wording up to you, just
>> expressing my original goal.
>
> "Innaccurate" is a good word, thanks Eli. I will make the changes
> and commit the patch tomorrow if nobody has any further objections.
To be honest, I don't like "inaccurate".
But I'm not going to push it.
next prev parent reply other threads:[~2012-03-15 19:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 13:38 Gary Benson
2012-03-14 17:51 ` Doug Evans
2012-03-14 17:55 ` Jan Kratochvil
2012-03-14 17:58 ` Doug Evans
2012-03-15 10:51 ` Gary Benson
2012-03-15 10:52 ` Jan Kratochvil
2012-03-15 16:51 ` Doug Evans
2012-03-15 18:04 ` Eli Zaretskii
2012-03-15 18:10 ` Gary Benson
2012-03-15 18:15 ` Eli Zaretskii
2012-03-15 18:26 ` Gary Benson
2012-03-15 18:31 ` Pedro Alves
2012-03-15 18:36 ` Eli Zaretskii
2012-03-15 18:40 ` Jan Kratochvil
2012-03-15 19:29 ` Gary Benson
2012-03-15 19:34 ` Doug Evans [this message]
2012-03-15 19:52 ` Pedro Alves
2012-03-15 20:06 ` Pedro Alves
2012-03-16 10:03 ` Gary Benson
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=CADPb22Rq4kDOJKWpX94dk_0N2g+EAc44UTCZynZSGpdujkfxmg@mail.gmail.com \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark@klomp.org \
--cc=palves@redhat.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