Strange segfaults of gdb

[Michal Ludvig]

Terje Eggestad wrote:
> One other detail, when you get a seg fault, or just simply break on a 
> symbol in libc, like strlen(), (first noticed it b/c a seg fault in 
> strlen) neither bt or where give the stack trace... That's a bug, right?

Well, it depends on the point of view :-)
These functions don't have a debug info, because they are pure assembler 
functions not written in C (applies to memcpy, str*, and some others, as 
well as for syscall wrappers). Without a valid Dwarf2 information GDB 
can't do a backtrace. However I don't treat this as a GDB bug, but 
anyway I'm implementing a workaround for this, because I know it's 
annoying :-)

Michal Ludvig
-- 
* SuSE CR, s.r.o     * mludvig@suse.cz
* (+420) 296.545.373 * http://www.suse.cz