On 10-Mar-2006, LUK ShunTim wrote: | I'm experiencing random crashes of octave 2.9.4 on a debian/sid box. I | apt-get the source and rebuild with debug on and here is the backtrace. | | <backtrace> | | $ gdb octave | GNU gdb 6.4-debian | Copyright 2005 Free Software Foundation, Inc. | GDB is free software, covered by the GNU General Public License, and you are | welcome to change it and/or distribute copies of it under certain | conditions. | Type "show copying" to see the conditions. | There is absolutely no warranty for GDB. Type "show warranty" for details. | This GDB was configured as "i486-linux-gnu"...(no debugging symbols found) | Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". | | (gdb) run | Starting program: /usr/bin/octave | (no debugging symbols found) | (no debugging symbols found) | (no debugging symbols found) | (no debugging symbols found) | (no debugging symbols found) | (no debugging symbols found) | (no debugging symbols found) | (no debugging symbols found) | (no debugging symbols found)
If you rebuilt with debugging enabled, then what happened to the symbols? Were they stripped at some point? | #1 0xb7b3b38d in octave_builtin::do_multi_index_op () | from /usr/lib/octave-2.9.4/liboctinterp.so With debugging symbols, I'd expect more info about the arguments. In any case, if it is truly a random crash that you can't reproduce, then the first thing I would check would be your system's memory. OTOH, if it is always crashing in the same place, then can you try to find some recipe for the failure? jwe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
