From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Sterling Augustine <saugustine@google.com>,
Cary Coutant <ccoutant@google.com>,
tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: Regressions with dwz [Re: [RFA] Work around binutils/15021]
Date: Thu, 24 Jan 2013 19:08:00 -0000 [thread overview]
Message-ID: <20130124190802.GA23093@host2.jankratochvil.net> (raw)
In-Reply-To: <20130124171608.GA14997@host2.jankratochvil.net>
On Thu, 24 Jan 2013 18:16:08 +0100, Jan Kratochvil wrote:
> On Thu, 24 Jan 2013 18:14:02 +0100, Doug Evans wrote:
> > Not sure I tested dwz with -m.
> > At any rate I get the same failures with a tree checked out with
> > -D2013-01-22 (i.e., before my patch).
>
> I get full PASS for ceb4ee95539d6324ca0f307ba729ea660ed5d1bd^ (see the
> trailing '^').
Correction: It was already broken just with the contrib/cc-with-tweaks.sh flag
"-m" (dwz).
But with "-m -i" (dwz together with .gdb_index) this commit regressed it.
("-m -i" is what gets exposed in Fedora packaging.)
Sure the "-m" issue is a bug, unaware now whether in dwz or in GDB (guessing
GDB).
Thanks,
Jan
next prev parent reply other threads:[~2013-01-24 19:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 23:21 [RFA] Work around binutils/15021 Doug Evans
2013-01-17 17:53 ` Tom Tromey
2013-01-17 18:42 ` Doug Evans
2013-01-17 21:04 ` [RFA, doc RFA] " Doug Evans
2013-01-18 7:17 ` Eli Zaretskii
2013-01-18 14:32 ` Tom Tromey
2013-01-24 14:59 ` Regressions with dwz [Re: [RFA] Work around binutils/15021] Jan Kratochvil
[not found] ` <CADPb22SoND17XeXBL2N+-DXf+yKuWe4PJEXR86qT06-q_LA+7g@mail.gmail.com>
2013-01-24 17:16 ` Jan Kratochvil
2013-01-24 19:08 ` Jan Kratochvil [this message]
2013-01-30 20:41 ` Tom Tromey
2013-06-09 17:09 ` [RFA] Work around binutils/15021 Jan Kratochvil
2013-06-12 9:49 ` Doug Evans
2013-06-12 18:29 ` Jan Kratochvil
2013-06-12 19:50 ` Cary Coutant
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=20130124190802.GA23093@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=ccoutant@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=saugustine@google.com \
--cc=tromey@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