From: "Doug Evans" <dje@google.com>
To: gdb-patches@sourceware.org
Cc: ARistovski@qnx.com
Subject: Re: [RFA] patch for DW_AT_comp_dir/DW_AT_name vs .debug_line inconsistencies
Date: Sat, 05 Jan 2008 22:49:00 -0000 [thread overview]
Message-ID: <e394668d0801051449q77188ba6xa8b291861d6c7210@mail.gmail.com> (raw)
In-Reply-To: <e394668d0801051418n3c9ab850l17a181dbbcedb134@mail.gmail.com>
[btw, this is my interpretation of Daniel's suggestion,
http://sourceware.org/ml/gdb/2008-01/msg00012.html,
all gaffes are mine of course]
On Jan 5, 2008 2:18 PM, Doug Evans <dje@google.com> wrote:
> Ref: http://sourceware.org/ml/gdb/2008-01/msg00007.html
>
> [Also ref: http://sourceware.org/ml/gdb-patches/2007-11/msg00314.html
> but I'm agnostic as to whether gdb should handle #line like this. The
> testcases in this patch use #line for convenience only.]
>
> How about this?
> Aleksandar, does this work for you? [you'll need to still account for
> IS_ABSOLUTE_PATH issues I suspect]
>
> This patch has dwarf_decode_lines prescan the .debug_line info for
> files that match DW_AT_name of the main source file, and passes that
> to start_subfile instead of what's recorded in .debug_line. This lets
> start_subfile get a match with the initial subfile created by
> start_symtab.
>
> I took an easy out in scanning for a match, I just pick the first. I
> can add the requisite code if folks think this is the way to go.
>
> No regressions in the testsuite (i686-linux).
>
next prev parent reply other threads:[~2008-01-05 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 22:18 Doug Evans
2008-01-05 22:49 ` Doug Evans [this message]
2008-01-07 2:25 Doug Evans
2008-04-08 9:29 Doug Evans
2008-04-09 13:33 ` Doug Evans
2008-04-17 16:21 ` Daniel Jacobowitz
2008-04-17 17:28 ` Doug Evans
2008-04-17 17:37 ` Daniel Jacobowitz
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=e394668d0801051449q77188ba6xa8b291861d6c7210@mail.gmail.com \
--to=dje@google.com \
--cc=ARistovski@qnx.com \
--cc=gdb-patches@sourceware.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