From: Joe M. <gm...@no...> - 2004-08-11 15:33:59
|
Hi UML developers, I am getting a variety of cores from UML - fairly intermittent. The bad part is that examining these cores with GDB is utterly fruitless (for me). Are there some tricks beyond the normal stuff below I should be doing to get a better sense of what is going wrong? I see no back trace and no thread info. thanks for any help, Giovanni [root@wbl6y227 plankton]# /usr/local/builds/gdb-6.2/gdb/gdb -c /bne/home/gmarzot/proj/celp/cores/core_sanity_crash_8_11 celp/linux.celp GNU gdb 6.2 Copyright 2004 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 "i686-pc-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". Core was generated by `/vob/neptune/plankton/celp/linux.celp (CSC-0-4-0) [/sbin/modprobe] '. Program terminated with signal 11, Segmentation fault. #0 0x00000000 in ?? () (gdb) where #0 0x00000000 in ?? () (gdb) bt #0 0x00000000 in ?? () (gdb) info thr * 1 process 12718 0x00000000 in ?? () warning: Couldn't restore frame in current thread, at frame 0 0x00000000 in ?? () (gdb) |