From: Daniel Jacobowitz <drow@false.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, iam ahal <hal9000ed2k@gmail.com>,
Tom Tromey <tromey@redhat.com>, Eli Zaretskii <eliz@gnu.org>,
palves@redhat.com, dje@google.com, pmuldoon@redhat.com,
brobecker@adacore.com, asmwarrior@gmail.com
Subject: Re: [commit] Handle files without DW_AT_comp_dir
Date: Sat, 07 Apr 2012 22:37:00 -0000 [thread overview]
Message-ID: <CAN9gPaE6QYMtpT2pL64JcvKhKYmQuSQ4Qo0ii9bQ0rJvhiV21Q@mail.gmail.com> (raw)
In-Reply-To: <20120406123641.GA18063@host2.jankratochvil.net>
On Fri, Apr 6, 2012 at 8:36 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> I do not see any problem with it, compilation directory is not known in such
> case. I do not see any testcase in this patch which would show which GCC
> versions under which conditions produced such buggy output. These GCC
> versions produce correct output, that is:
I'm sure it was the current stable GCC at the time. That would be
4.1/4.2. I'd try to find the fix, but picking out a patch by Joseph
is like hunting for a needle in a haystack :-)
> Without known GCC buggy versions going to revert this patch as it breaks
> correct DWARF. The thread "that cuts path to file (remain filename)" tries to
> (in some way) undo what this patch does.
Can you explain the way in which this breaks correct DWARF? I'm
confused since the description of the other thread sounds like an
output issue, not a debug reader issue...
--
Thanks,
Daniel
next prev parent reply other threads:[~2012-04-07 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 12:36 Daniel Jacobowitz
2012-04-06 12:37 ` Jan Kratochvil
2012-04-07 22:37 ` Daniel Jacobowitz [this message]
2012-04-07 23:27 ` Joseph S. Myers
2012-04-09 15:48 ` Jan Kratochvil
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=CAN9gPaE6QYMtpT2pL64JcvKhKYmQuSQ4Qo0ii9bQ0rJvhiV21Q@mail.gmail.com \
--to=drow@false.org \
--cc=asmwarrior@gmail.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hal9000ed2k@gmail.com \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=pmuldoon@redhat.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