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:51:00 -0000	[thread overview]
Message-ID: <2F6320727174C448A52CEB63D85D11F40A72@nova.ott.qnx.com> (raw)

 
> I do not see how the text you quoted has any bearing on this
> situation.

Daniel, let me recap:

My gcc 3.3.5 output:
     DW_AT_name        :
c:/QNXTau/eclipse/ide-4.5-workspace/testManagedCC/main.cc
     DW_AT_comp_dir    :
c:/QNXTau/eclipse/ide-4.5-workspace/testManagedCC/Debug
...
The Directory Table:
  ..

 The File Name Table:
  Entry	Dir	Time	Size	Name
  1		1	0	0	main.cc

My gcc 4.2.1 output:
    DW_AT_name        : ..\main.cc
     DW_AT_comp_dir    :
C:\QNXTau\eclipse\ide-4.5-workspace\testManagedCC\Debug
...
The Directory Table is empty.

 The File Name Table:
  Entry Dir Time	Size	Name
  1	  0	0	0	..\main.cc


Following the spec, I conclude that

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.

2. case 4.2.1:
DW_AT_name is correct, according to point 2 of quoted document.
DW_AT_comp_dir is also correct and 
file table in debug_line seems to be correct too.


You suggested that output from case 3.3.5 was a bug and should not occur (I
thought your statement: "The compiler should never do this.  I still say
that this is a bug in the compiler.  " was referring to this situation,
apologies if I misinterpreted what you said). 

Does it make sense now? 


Thanks,

Aleksandar


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

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 21:51 Aleksandar Ristovski [this message]
2008-01-08 21:57 ` 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: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=2F6320727174C448A52CEB63D85D11F40A72@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