[kdelibs] [Bug 331784] Kded4 crashes when RANDR is disabled.

[Neil Whelchel]

https://bugs.kde.org/show_bug.cgi?id=331784

--- Comment #2 from Neil Whelchel <neil.whelchel at gmail.com> ---
I had a look at the link that was provided about generating a useful crash
report, but there is literally nothing there that helps the situation. I set
ulimit -c unlimited, but no core is generated. so I did the following:
gdb kded4
(gdb) run
Starting program: /usr/bin/kded4 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
gobject.py: gdb was not built with custom backtrace support, disabling.
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
kded(25363) ColorD::connectToDisplay: RandR extension missing 
kded(25363) ColorD::ColorD: Failed to connect to DISPLAY and get the needed
resources 
Xlib:  extension "RANDR" missing on display ":0".
Xlib:  extension "RANDR" missing on display ":0".
Can't get XRandR version 
kded4: Fatal IO error: client killed
kded(25353): Communication problem with  "kded" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not
receive a reply (timeout by message bus)" " 

[Inferior 1 (process 25353) exited with code 0377]
(gdb) bt
No stack.
(gdb) info inferiors
  Num  Description       Executable        
* 1    <null>            /usr/bin/kded4    
(gdb) inferior 1
[Switching to inferior 1 [<null>] (/usr/bin/kded4)]
(gdb) bt
No stack.
(gdb)

So I ran a trace on the inferior and the last system call it makes is
exit_group(1), so I added a trap:

(gdb) catch syscall exit_group
Catchpoint 1 (syscall 'exit_group' [231])
(gdb) run
<same output as last run with exception of pid number>
Catchpoint 1 (call to syscall exit_group), 0x00007ffff78c4f69 in __GI__exit
(status=status at entry=255) at ../sysdeps/unix/sysv/linux/_exit.c:32
32      ../sysdeps/unix/sysv/linux/_exit.c: No such file or directory.
(gdb) bt
#0  0x00007ffff78c4f69 in __GI__exit (status=status at entry=255) at
../sysdeps/unix/sysv/linux/_exit.c:32
#1  0x00007ffff783f4cb in __run_exit_handlers (status=255, listp=<optimized
out>, run_list_atexit=run_list_atexit at entry=true) at exit.c:97
#2  0x00007ffff783f555 in __GI_exit (status=<optimized out>) at exit.c:104
#3  0x00007ffff70af1ba in KUniqueApplication::start (flags=...) at
../../kdeui/kernel/kuniqueapplication.cpp:183
#4  0x00007ffff70afa13 in KUniqueApplication::start () at
../../kdeui/kernel/kuniqueapplication.cpp:110
#5  0x00007ffff7bd35aa in kdemain (argc=1, argv=0x7fffffffde58) at
../../kded/kded.cpp:893
#6  0x00007ffff7824ec5 in __libc_start_main (main=0x4006d0 <main(int, char**)>,
argc=1, argv=0x7fffffffde58, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, 
    stack_end=0x7fffffffde48) at libc-start.c:285
#7  0x00000000004006fe in _start ()
(gdb)


Still, nothing of use...
This explains the absence of a core file, it looks like kded4 hit a return, not
a crash.
How do I debug this one?

-- 
You are receiving this mail because:
You are the assignee for the bug.