https://bugzilla.novell.com/show_bug.cgi?id=327583#c2
Andrew Horoszczak changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|ah@forex.pl |
--- Comment #2 from Andrew Horoszczak 2007-09-24 12:27:56 MST ---
Well I guess it was the problem with stack that was responsible for lack of
backtrace (and not the debug packages) - still I have no idea why gdb cannot
access stack ?? what should I do?
Anyway I am marking remove NEEDINFO, because there is at least line number
resposible for this particular assert:
andrzej@linx:~/> gdb kdesktop_lock
GNU gdb 6.6.50.20070726-cvs
Copyright (C) 2007 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i586-suse-linux"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run --forcelock
Starting program: /opt/kde3/bin/kdesktop_lock --forcelock
[Thread debugging using libthread_db enabled]
[New Thread 0xb5aa26d0 (LWP 4703)]
krandom.kss: xcb_xlib.c:52: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
KCrash: Application 'krandom.kss' crashing...
Program exited normally.
(gdb) bt
No stack.
(gdb)
--
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.