[yast-devel] New 'gdb' section in the YaST bug reporting howto
Hi all, 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). So if you need a backtrace for debugging you can use the link to this section: http://en.opensuse.org/Bugs/YaST#How_can_I_start_YaST_in_debugger_.28gdb.29.... If you find a bug or you have any improvement then just edit the page, it's a wiki. Ladislav -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hi! Thanks for it! Just one question (since I have never tried the scenario): Could this work also during installation (from the second console)? I know that we do not have the debuginfo packages available, anyway, getting the core dump even without debuginfo may be useful... Jiri Dne Tuesday 02 of October 2007 09:41:44 Ladislav Slezak napsal(a):
Hi all,
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).
So if you need a backtrace for debugging you can use the link to this section: http://en.opensuse.org/Bugs/YaST#How_can_I_start_YaST_in_debugger_.28gdb.29 .3F_How_can_I_create_a_backtrace.3F
If you find a bug or you have any improvement then just edit the page, it's a wiki.
Ladislav
--
Best Regards
Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/
-- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz
Jiri Srain napsal(a):
Hi!
Thanks for it!
Just one question (since I have never tried the scenario): Could this work also during installation (from the second console)? I know that we do not have the debuginfo packages available, anyway, getting the core dump even without debuginfo may be useful...
Yes, it should work even in inst-sys (it's possible to attach gdb to the running Yast). -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Ladislav Slezak napsal(a):
Jiri Srain napsal(a):
Hi!
Thanks for it!
Just one question (since I have never tried the scenario): Could this work also during installation (from the second console)? I know that we do not have the debuginfo packages available, anyway, getting the core dump even without debuginfo may be useful...
Yes, it should work even in inst-sys (it's possible to attach gdb to the running Yast).
...and it's also possible to start the installation with 'textmode=1' Linuxrc-parameter and edit YaST scripts to start y2base in gdb. Anyway, this is a requested feature :) Something like: 'RUNINGDB=1' and then YaST should be started in gdb with any need to modify anything. I'm thinking now that it seems to be pretty easy... Lukas
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. Any volunteers? CU -- Stefan Hundhammer <sh@suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
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
On Tue, Oct 02, 2007 at 03:39:57PM +0200, Michal Svec wrote:
On Tue, 2 Oct 2007, Stefan Hundhammer wrote:
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.
http://www.gnu.org/software/libc/manual/html_node/Backtraces.html Yes, we have thought of that, and noted it in a FATE item about debugging: https://keeper.suse.de/webfate/match/id?value=302167 I think I will first try the glibc thing because it is only little more difficult and does not need gdb. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (6)
-
Jiri Srain -
Ladislav Slezak -
Lukas Ocilka -
Martin Vidner -
Michal Svec -
Stefan Hundhammer