1/1 
|
FRAME_POINTER_REQUIRED
by Unknown on Jan 12, 2004 |
Not available! | ||
|
Hey !
I don't use backtrace but yes if you want to use it you have to compile
with -fno-omit-frame-pointer at least in theory. If it actually works we
will soon find out from you ;-)
regards,
Damjan
----- Original Message -----
From: "Heiko Panther" heiko.panther@web.de>
To: openrisc@opencores.org>
Sent: Monday, January 12, 2004 6:55 PM
Subject: [openrisc] FRAME_POINTER_REQUIRED
Does anyone know about this.
I was researching why I don't get a backtrace while debugging my
optimized program, and found that gcc does not build a stack frame for
the breakpoint() function. But opencores gdb tries to read the return
address from the stack frame, so that's why it fails.
I see that there is
#define FRAME_POINTER_REQUIRED 0
in or32.h.
Is this the reason? Does anyone do debugging with optimized binaries? I
will try to set FRAME_POINTER_REQUIRED to 1 and see if that works. There
is also a compiler option -fomit-frame-pointer, I'm gonna try
-fno-omit-frame-pointer.
Heiko
_______________________________________________
http://www.opencores.org/mailman/listinfo/openrisc
|
|||
|
FRAME_POINTER_REQUIRED
by Unknown on Jan 12, 2004 |
Not available! | ||
|
Does anyone know about this.
I was researching why I don't get a backtrace while debugging my optimized program, and found that gcc does not build a stack frame for the breakpoint() function. But opencores gdb tries to read the return address from the stack frame, so that's why it fails. I see that there is #define FRAME_POINTER_REQUIRED 0 in or32.h. Is this the reason? Does anyone do debugging with optimized binaries? I will try to set FRAME_POINTER_REQUIRED to 1 and see if that works. There is also a compiler option -fomit-frame-pointer, I'm gonna try -fno-omit-frame-pointer. Heiko |
|||
1/1