-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 27 November 2003 17:46, Fernando Fernandez wrote: > is this because the segmentation thing i mentioned before???? this i > beginning to be a pain... why are things failing to launch??? Pick a segfaulting app and run it under gdb gdb --args /path/to/program any-args-go-here For example, I used gdb --args /usr/bin/mplayer badvideo.wmv Type (gdb) run to start it up. When it crashes, you'll see something like Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1084798560 (LWP 8541)] 0x0071fb22 in _int_malloc () from /lib/tls/libc.so.6 and you'll get the debugger prompt. Type (gdb) bt To get a stack trace from the faulting thread, something like #0 0x0071fb22 in _int_malloc () from /lib/tls/libc.so.6 #1 0x0071ee7d in malloc () from /lib/tls/libc.so.6 #2 0x008344c1 in _XUpdateAtomCache () from /usr/X11R6/lib/libX11.so.6 #3 0x0082ec0e in XGetAtomName () from /usr/X11R6/lib/libX11.so.6 #4 0x080a43d9 in vo_x11_check_events () This gives you the clue of the execution path through the app and libraries, this is often very meaningful for finding the problem. (gdb) quit exits you back to the shell. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/xjxojKeDCxMJCTIRAnE7AJ9uk5iiwpcN25gE/SbccU0knX0FhQCeMK32 dxtx9hgLvB2K/wvHp2BBTcE= =oKjg -----END PGP SIGNATURE-----
