Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Aleksandar Ristovski <ARistovski@qnx.com>
To: Daniel Jacobowitz <drow@false.org>
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:24:00 -0000	[thread overview]
Message-ID: <2F6320727174C448A52CEB63D85D11F40A6F@nova.ott.qnx.com> (raw)

> 
> Aha!  Thanks for checking, that looks much more promising.

But it won't go away...


Dwarf3 spec (December 20, 2007), page 38, points 2. and 6.:

2.	A DW_AT_name attribute whose value is a null-terminated string
containing the full or relative path name of the primary source file from
which the compilation unit was derived.
....
6.	A DW_AT_comp_dir attribute whose value is a null-terminated string
containing the current working directory of the compilation command that
produced this compilation unit in whatever form makes sense for the host
system. 
The suggested form for the value of the DW_AT_comp_dir attribute on UNIX
systems is "hostname:pathname". If no hostname is available, the suggested
form is ":pathname".

(I find this 'suggested form' particularly scary).

Dwarf2 spec (Industry Review Draft, Revision: 2.0.0, July 27, 1993)
specifies exactly the same.


I don't know how do you interpret this, but I would say the output from my
example produced by 3.3.5 is also correct.



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

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 21:24 Aleksandar Ristovski [this message]
2008-01-08 21:32 ` Daniel Jacobowitz
  -- 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:51 Aleksandar Ristovski
2008-01-08 21:57 ` Daniel Jacobowitz
2008-01-08 21:26 Aleksandar Ristovski
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=2F6320727174C448A52CEB63D85D11F40A6F@nova.ott.qnx.com \
    --to=aristovski@qnx.com \
    --cc=RMansfield@qnx.com \
    --cc=dje@google.com \
    --cc=drow@false.org \
    --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