Havoc Pennington writes:

 > It's probably caused by the first error. If you want to try to track
 > down how, run with --sync in gdb to trap the backtrace where the X
 > error occurs.

OK, that sounds useful. Since I haven't used gdb you explain me how to
do that? The program I'm trying to run is interpreted python code; the
bug is presumably in one or another shared library. Also, I'm looking
at the Info file on gdb, but I can't find anything about a --sync
option.

Thanks,

Matt Gushee

-- 
To unsubscribe: mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Reply via email to