[prev in list] [next in list] [prev in thread] [next in thread] 

List:       licq-devel
Subject:    [Licq-devel] Debugging LICQ/Window Maker crash
From:       Petter =?iso-8859-1?Q?Sundl=F6f?= <petter.sundlof () findus ! dhs ! org>
Date:       2002-01-29 17:09:31
[Download RAW message or body]

Hi.

I've been trying to run LICQ through GDB, to get to the root of a Window
Maker crash I've been having. It happens after I've been running
LICQ/GTK+LICQ for quite  a while, and is triggered by simply double
clicking a contact to send a message. The following errors are shown in
stdout:

Gdk-WARNING **: GdkWindow 0x1000698 unexpectedly destroyed
Gdk-ERROR **: BadWindow (invalid Window parameter)
  serial 151147 error_code 3 request_code 129 minor_code 2
wmaker: trying to restart Window Maker...

I don't know if this tells you developers anything?

So, when I try to run it in GDB...

$ gdb licq
[...]
(gdb) run
[...]
Program received signal SIG32, Real-time event 32.
0x40260ace in sigsuspend () from /lib/libc.so.6

 Okay, I simply do:

(gdb) handle SIG32 pass nostop

 and

(gdb)continue

 but then I get:

Program received signal SIGTRAP, Trace/breakpoint trap.
0x40260ace in sigsuspend () from /lib/libc.so.6

(gdb)bt
#0  0x40260ace in sigsuspend () from /lib/libc.so.6
#1  0x401a96b9 in pthread_getconcurrency () from /lib/libpthread.so.0
#2  0x401a5f12 in pthread_cond_wait () from /lib/libpthread.so.0
#3  0x08060f46 in CLicq::Main ()
#4  0x080618e7 in main ()
#5  0x4025074f in __libc_start_main () from /lib/libc.so.6

Is there any way to debug LICQ? Using CVS from Jan 27/28, and latest
GTK+LICQ in CVS.

Best regards,
Petter Sundlöf

_______________________________________________
Licq-devel mailing list
Licq-devel@licq.org
https://lists.sourceforge.net/lists/listinfo/licq-devel
[prev in list] [next in list] [prev in thread] [next in thread]