On Sun October 25 2009 12:53:32 am Mark wrote: > It's 1 am so I'm off to sleep but I will give the debugger a shot tomorrow.
Ok, it's been more like a week. :) Peter C., You'll find the back trace in the attached file. I had to run it with the --sync command otherwise trace would be empty. The only thing that concerns me was having to press Ctrl+C in the debugger after the program crashed. I made a note about it in the file but I'm just not sure how it affected the back trace. -Mark Stanley
~$ gdb -q pcb (gdb) set args --sync (gdb) run Starting program: ~/apps/geda/bin/pcb --sync Loading file ~/projects/icd2_clone.pcb took 0.550000 The program 'pcb' received an X Window System error. This probably reflects a bug in the program. The error was 'BadColor (invalid Colormap parameter)'. (Details: serial 80612 error_code 12 request_code 79 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) **** At this point pcb is at 100% CPU usage so I have to Ctrl+C to stop it **** and regain control of gdb. Program received signal SIGINT, Interrupt. 0xb789868e in _XGetXCBBuffer () from /usr/lib/libX11.so.6 (gdb) bt #0 0xb789868e in _XGetXCBBuffer () from /usr/lib/libX11.so.6 #1 0xb78991a3 in ?? () from /usr/lib/libX11.so.6 #2 0x081ca478 in ?? () #3 0xb736615c in ?? () from /usr/lib/libxcb.so.1 #4 0xbf926678 in ?? () #5 0xb78986a1 in _XGetXCBBuffer () from /usr/lib/libX11.so.6 #6 0xb78995aa in _XReply () from /usr/lib/libX11.so.6 #7 0xb788d7ba in XSync () from /usr/lib/libX11.so.6 #8 0xb788d935 in ?? () from /usr/lib/libX11.so.6 #9 0x081ca478 in ?? () #10 0x00000000 in ?? () **** Here are the other processes that failed to exit properly. 3368 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 8 --print-address 10 --session **** I repeated the back trace twice more to ensure I was getting good information. **** I restarted the computer each time. They look a little different each time. -------------------------------- Program received signal SIGINT, Interrupt. 0xb7366284 in _xcb_lock_io () from /usr/lib/libxcb.so.1 (gdb) bt #0 0xb7366284 in _xcb_lock_io () from /usr/lib/libxcb.so.1 #1 0xb73765b2 in xcb_xlib_unlock () from /usr/lib/libxcb-xlib.so.0 #2 0xb78a8168 in ?? () from /usr/lib/libX11.so.6 #3 0x081ca9b8 in ?? () #4 0xb737515c in ?? () from /usr/lib/libxcb.so.1 #5 0xbffbe508 in ?? () #6 0xb78a76a1 in _XGetXCBBuffer () from /usr/lib/libX11.so.6 #7 0xb78a85aa in _XReply () from /usr/lib/libX11.so.6 #8 0xb789c7ba in XSync () from /usr/lib/libX11.so.6 #9 0xb789c935 in ?? () from /usr/lib/libX11.so.6 #10 0x081ca478 in ?? () #11 0x00000000 in ?? () 3598 pts/2 S+ 0:00 dbus-launch --autolaunch 83ca96941b0d9abd04f9fd7c4954109a --binary-syntax --close-stderr 3599 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 8 --print-address 10 --session -------------------------------- Program received signal SIGINT, Interrupt. 0xb7465f7b in pthread_mutex_unlock () from /lib/libc.so.6 (gdb) bt #0 0xb7465f7b in pthread_mutex_unlock () from /lib/libc.so.6 #1 0xb7325660 in xcb_xlib_lock () from /usr/lib/libxcb-xlib.so.0 #2 0xb7857198 in ?? () from /usr/lib/libX11.so.6 #3 0x081ca9b8 in ?? () #4 0xb732415c in ?? () from /usr/lib/libxcb.so.1 #5 0xbfe0ab58 in ?? () #6 0xb78566a1 in _XGetXCBBuffer () from /usr/lib/libX11.so.6 #7 0xb78575aa in _XReply () from /usr/lib/libX11.so.6 #8 0xb784b7ba in XSync () from /usr/lib/libX11.so.6 #9 0xb784b935 in ?? () from /usr/lib/libX11.so.6 #10 0x081ca478 in ?? () #11 0x00000000 in ?? () 3040 pts/3 S 0:00 dbus-launch --autolaunch 83ca96941b0d9abd04f9fd7c4954109a --binary-syntax --close-stderr 3041 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 8 --print-address 10 --session
_______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user