This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/14423] Missing debug_line info for non-inline function call site with inline call in parameter
- From: "rdelashmit at soe dot sony dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 4 Mar 2004 15:44:09 -0000
- Subject: [Bug debug/14423] Missing debug_line info for non-inline function call site with inline call in parameter
- References: <20040304002203.14423.rdelashmit@soe.sony.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From rdelashmit at soe dot sony dot com 2004-03-04 15:44 -------
(In reply to comment #1)
> Looks to be fixed for both 3.3.1 and 3.4.0, can you try 3.3.3 and see if it
is fixed?
I tried 3.3.3, and dwarfdump is identical to that given using 3.2.3. I also
built and tested a cvs version from yesterday (3.5.0 20040303 (experimental))
and the relevant debug info is missing there as well. Below is the dwarfdump
for the 3.3.3 built file, and the 2.95.3 built file. Source lines 17 and 18
are the ones I would expect to be present that are missing from the 3.x built
file.
With 3.3.3:
line number info
<source> [row,column] <pc> //<new statement or basic block
/home/rdelashmit/gcctest/a.cpp: [ 11,-1] 0 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 12,-1] 0x3 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 13,-1] 0xb // new statement
/home/rdelashmit/gcctest/a.cpp: [ 16,-1] 0xe // new statement
/home/rdelashmit/gcctest/a.cpp: [ 6,-1] 0x17 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 5,-1] 0x21 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 6,-1] 0x2d // new statement
/home/rdelashmit/gcctest/a.cpp: [ 5,-1] 0x37 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 20,-1] 0x43 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 20,-1] 0x4e // new statement
// end of text sequence
With 2.95.3:
line number info
<source> [row,column] <pc> //<new statement or basic block
/home/rdelashmit/gcctest/a.cpp: [ 11,-1] 0x3 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 12,-1] 0x6 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 13,-1] 0xf // new statement
/home/rdelashmit/gcctest/a.cpp: [ 17,-1] 0x16 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 5,-1] 0x19 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 6,-1] 0x19 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 7,-1] 0x23 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 8,-1] 0x23 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 17,-1] 0x23 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 18,-1] 0x2a // new statement
/home/rdelashmit/gcctest/a.cpp: [ 5,-1] 0x2d // new statement
/home/rdelashmit/gcctest/a.cpp: [ 6,-1] 0x30 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 7,-1] 0x3a // new statement
/home/rdelashmit/gcctest/a.cpp: [ 8,-1] 0x3a // new statement
/home/rdelashmit/gcctest/a.cpp: [ 18,-1] 0x3a // new statement
/home/rdelashmit/gcctest/a.cpp: [ 19,-1] 0x41 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 20,-1] 0x47 // new statement
/home/rdelashmit/gcctest/a.cpp: [ 20,-1] 0x47 // new statement
// end of text sequence
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14423