Hard times debugging under KDevelop

[Josef Weidendorfer]

On Friday 23 January 2004 14:07, Andras Mantia wrote:
> (gdb) next <---- here I don't get back the gdb command prompt
>
> Program received signal SIGINT, Interrupt.
> 0x41a00a78 in write () from /lib/libpthread.so.0
> (gdb) info thread
> * 1 Thread 16384 (LWP 11288)  0x41a00a78 in write () from
> /lib/libpthread.so.0 (gdb) backtrace
> #0  0x41a00a78 in write () from /lib/libpthread.so.0
> #1  0x40ae2bb4 in __JCR_LIST__ () from /opt/kde-cvs/lib/libkio.so.4
> #2  0x4094a7b4 in KDirWatchPrivate::dnotify_sigio_handler(int, siginfo*,
> void*) () from /opt/kde-cvs/lib/libkio.so.4

SIGIO is passed to the program, and the signal handler tries to write into 
some pipe to trigger a QSocketNotifier, to delay any reaction into the QT 
main loop. Obviously, the write blocks. Perhaps the pipe is full.

Better don't use DNOTIFY in your case.

Josef






> #3  0x41a0093b in __pthread_sighandler_rt () from /lib/libpthread.so.0
> #4  <signal handler called>
> (gdb) info args
> No symbol table info available.
> (gdb) info local
> No symbol table info available.
> (gdb) frame 0
> #0  0x41a00a78 in write () from /lib/libpthread.so.0
>
> I've tried to play with "set scheduler-locking", but without success. By
> default it is set to "off".
>
> Any idea how can I debug my programs? It's very hard to do now.
> I use gdb 6.0 now (the same happened with 5.3), kernel 2.4.20 (suse), g++
> 3.3.1 (suse) and glibc 2.3.2.
>
> Andras
>
>
> - --
> Quanta Plus developer - http://quanta.sourceforge.net
> K Desktop Environment - http://www.kde.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
>
> iD8DBQFAERyxTQdfac6L/08RArzKAJ9tuXlBkra/WdkTBF2mS/oajiYJ3ACghx83
> DvchA2Ij6f2KHyxh5qhABLE=
> =qTMf
> -----END PGP SIGNATURE-----