From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>,
Mark Wielaard <mark@klomp.org>
Subject: Re: [RFA take 5] Allow setting breakpoints on inline functions (PR 10738)
Date: Thu, 23 Feb 2012 11:15:00 -0000 [thread overview]
Message-ID: <20120223095715.GA10868@host2.jankratochvil.net> (raw)
In-Reply-To: <CADPb22QpCHsbPd=BYpGM_+_ycwdvzk3ngKE2vZ+fRWj+ApD3OA@mail.gmail.com>
On Wed, 22 Feb 2012 17:56:41 +0100, Doug Evans wrote:
> On Wed, Feb 22, 2012 at 6:53 AM, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> > with some more discussions about it Tom also shares this opinion. Â I think
> > Google should just apply the provided patch downstream. Â Upstream/Gary should
> > drop that --allow-incomplete-gdb-indexes option completely, incl. dropping the
> > GDB code for backward compatibility with .gdb_index v4 and v5.
>
> Setting aside Google's needs,
> If I were allowed to decide, I would require v4,v5 compatibility for
> at least one release.
So if it is officially a temporary compatibility additionally to
--allow-smth-gdb-indexes GDB could print - if it finds out v4/v5 .gdb_index:
warning: Not using old .gdb_index v%d, rebuild it with this GDB version.
I have some doubts any user would ever use --allow-smth-gdb-indexes otherwise.
Regards,
Jan
next prev parent reply other threads:[~2012-02-23 9:57 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
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 [this message]
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=20120223095715.GA10868@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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