--- Additional Comments From wilson at gcc dot gnu dot org 2005-07-26
23:51 ---
The problem reported here is not a bug. There is nothing wrong with having two
different functions with the same DW_AT_ranges info.
The underlying problem that prompted this bug report, insufficient debug i
--- Additional Comments From wilson at gcc dot gnu dot org 2005-05-12
20:37 ---
Created an attachment (id=8881)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8881&action=view)
Emit DW_AT_call_file and DW_AT_call_line for inlined subroutines.
--
What|Removed
--- Additional Comments From wilson at gcc dot gnu dot org 2005-04-28
23:58 ---
Created an attachment (id=8760)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8760&action=view)
Emit DW_AT_call_file and DW_AT_CALL_line for inlined subroutines.
This emits extra debug info that descri
--- Additional Comments From wilson at gcc dot gnu dot org 2005-04-28
23:52 ---
My opinion is roughly the same as Daniel's. The debug info being emitted by gcc
here is fine.
The underlying problem here is that Fred is trying to improve support for
inlined function calls, and the curren
--- Additional Comments From drow at gcc dot gnu dot org 2005-04-12 14:08
---
Subject: Re: g++ generates same DW_AT_ranges info for two different functions
It's a question of what "associated machine code" means. I think that
the machine code is in fact associated with more than one D
--- Additional Comments From fnf at specifixinc dot com 2005-04-12 14:00
---
> No version information. Is this HEAD, with Jim's earlier DW_AT_ranges patch?
Yes, sorry I didn't mention it. Originally I tried to report this bug with
"gccbug" but the report seems to have gone into a blac
--- Additional Comments From drow at gcc dot gnu dot org 2005-04-12 13:14
---
No version information. Is this HEAD, with Jim's earlier DW_AT_ranges patch?
I don't think your understanding is correct, but you didn't show enough of the
DIE tree to be sure. Ignore inlined functions for a
