https://bugzilla.novell.com/show_bug.cgi?id=394408
User casualprogrammer@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=394408#c7
--- Comment #7 from Casual J. Programmer 2008-05-30 10:23:10 MDT ---
Well I thought debugging had to be done as root, never mind. Running as root
shouldn't cause a crash, artificial nor otherwise.
Will repeat as normal user then.
:~> killall gpk-update-icon
gpk-update-icon: no process killed
:~> gdb gpk-update-icon
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i586-suse-linux"...
(gdb) run
Starting program: /usr/bin/gpk-update-icon
[Thread debugging using libthread_db enabled]
[New Thread 0xb71468d0 (LWP 13473)]
------------------------------------------------------------------------
At this point message box opens "Failed to reset client. Failed to reset
get-updates. Close"
Pressing Close then is followed by:
------------------------------------------------------------------------
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb71468d0 (LWP 13473)]
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0x00000000 in ?? ()
(gdb) q
The program is running. Exit anyway? (y or n) y
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.