On Tue, 2 Oct 2007, Stefan Hundhammer wrote:
On Tuesday 02 October 2007 09:41, Ladislav Slezak wrote:
I just have added a new section into the YaST bug reporting howto (http://en.opensuse.org/Bugs/YaST). There is a new section 1.13 which describes how to start Yast in gdb debugger. This is usually needed when Yast crashes (segfault).
Just a thought: Back in the mid-1990s some medical imaging software on SunOS did something pretty clever with segfaults: They had let the process dump core, then automatically invoke the debugger and make it dump the stack trace to a file. Maybe we could do that, too. Our startup scripts already detect segfaults IIRC, so generating the stack trace should not be so hard to do.
BTW there is also some support for backtraces in glibc, I don't remember the exact calls, and I'm also not sure if it's usable/useful meanwhile. Michal -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org