Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Aleksandar Ristovski <ARistovski@qnx.com>
Cc: dje@google.com, gdb-patches@sourceware.org,
		Ryan Mansfield <RMansfield@qnx.com>
Subject: Re: [RFA] patch for DW_AT_comp_dir/DW_AT_name vs .debug_line inco 	nsistencies
Date: Tue, 08 Jan 2008 21:57:00 -0000	[thread overview]
Message-ID: <20080108215647.GA12656@caradoc.them.org> (raw)
In-Reply-To: <2F6320727174C448A52CEB63D85D11F40A72@nova.ott.qnx.com>

On Tue, Jan 08, 2008 at 04:51:02PM -0500, Aleksandar Ristovski wrote:
> 1. case 3.3.5:
> DW_AT_name is correct, according to point 2 of quoted document.
> DW_AT_comp_dir is correct, according to point 6 of the quoted text.
> File table in debug_line section is correct (according to the spec) as it
> specifies files relative to DW_AT_comp_dir.

You can't use the DWARF specification like this.  It describes a
representation, but not all the semantics of the representation; there
are plenty of things that appear valid according to the specification
and are still broken or meaningless.  In the end you have to judge the
debug info based on its usefulness to consumers.

The compiler specifies the same directory using two completely
different names.  I think this is a bug in the compiler, and that GDB
is not obliged to figure out that the two files are the same.

If you still need GDB to figure this out, I am open to a patch which
handles the case of a single entry in the line table with the correct
basename (i.e. if there is only one "main.c").  For any more
complicated situation, I think that guessing is too likely to break
some other case with more useful debug information.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-01-08 21:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 21:51 Aleksandar Ristovski
2008-01-08 21:57 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-09 14:55 Aleksandar Ristovski
2008-04-09 20:52 ` Doug Evans
2008-04-08 16:37 Aleksandar Ristovski
2008-01-08 21:26 Aleksandar Ristovski
2008-01-08 21:24 Aleksandar Ristovski
2008-01-08 21:32 ` Daniel Jacobowitz
2008-01-08 20:28 Aleksandar Ristovski
2008-01-08 20:33 ` Daniel Jacobowitz
2008-01-08 16:34 Aleksandar Ristovski
2008-01-08 16:46 ` Daniel Jacobowitz
2008-01-08 16:10 Aleksandar Ristovski
2008-01-08 16:19 ` Daniel Jacobowitz
2008-01-08 17:33 ` Doug Evans
2008-01-06  6:44 Aleksandar Ristovski
2008-01-06 18:44 ` Doug Evans

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=20080108215647.GA12656@caradoc.them.org \
    --to=drow@false.org \
    --cc=ARistovski@qnx.com \
    --cc=RMansfield@qnx.com \
    --cc=dje@google.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