This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/17994] avr-gcc does not output a dwarf2 .debug_frame section
- From: "bjoern dot m dot haase at web dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 May 2005 13:59:33 -0000
- Subject: [Bug target/17994] avr-gcc does not output a dwarf2 .debug_frame section
- References: <20041014082220.17994.tsandnes@atmel.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From bjoern dot m dot haase at web dot de 2005-05-06 13:59 -------
Hi,
I have been reviewing PR19885 and come to the following conclusions:
1.) As expected, Torleif is right: I can confirm that the problem exists,
2.) it should, however, probably be called rather a request for enhancement
than a bug: Beside call stack information the debugging info should be ok in
principle.
3.) There seems to be only one little part missing in order to add the call
stack information as well: The back-end needs to provide the information at
which memory address the debugger could localize the return address. This would
require to implement the target hook INCOMING_RETURN_ADDR_RTX and use the
RTX_FRAME_RELATED_P predicate for all of the prologue/epilogue insn.
I think the best way to address this issue would be to resolve this issue
simultaneously when switching from asm-prologue/epilogue to
RTL-prologue/epilogue. Since Andy Hutchinson is just working on this issue, we
might soon have a solution. Hopefully :-). Would be very helpfull to have call
stack info in avrstudio.
Yours,
Bjoern
P.S.:
I hope you will not be flaming me for adding you on the CC list. :-) Just
thought that you might be interrested since I know you are working on the
prologue/epilogue issue.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |hutchinsonandy at netscape
| |dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17994