Hi,
This finally did the trick. I configured and compiled glibc using
./configure [...] CFLAGS=-g -O2 -fno-omit-frame-pointer
Now the backtrace doesn't repeat forever, although I still get
Previous frame identical to this frame (corrupt stack?).
To debug functions which do not return (have
On Tuesday 18 July 2006 19:35, Christian Henz wrote:
The compilation of glibc did not explicitly use -fomit-frame-pointer, but
the GCC manual states that -O implies it on architectures where it
doesn't break debugging. Unfortunately it doesn't mention which
architectures those are. I'm
On Friday 14 July 2006 08:37, Eero Tamminen wrote:
Hi,
On the Nokia 770, the backtrace goes on forever and i have to kill gdb
Have you compiled your binary:
- without optimization (or used -no-omit-frame-pointer)
- with -g
- not stripped it
?
If not, if you do that and try again, does
Hi,
I simply compiled with -g before, adding the -no-omit-frame-pointer
directive did not help.
Actually I think the library where the function giving infinite
backtrace is should be compiled with -g (or debug package for
it should be installed). If that doesn't help then you need
to compile
Hi,
On the Nokia 770, the backtrace goes on forever and i have to kill gdb
Have you compiled your binary:
- without optimization (or used -fno-omit-frame-pointer)
- with -g
- not stripped it
?
If not, if you do that and try again, does the debugging work better?
If it still doesn't work, does
