On Sat, Nov 13, 2004 at 08:35:00AM +0100, Mirar @ Pike developers forum wrote:
See if you can get it to crash inside the gdb, and then run "call gdb_backtraces()" while you still have a process. It will print where it is in your pike program.
This gives:
--snip-- Starting program: /home/aldem/src/pike/cvs/Pike-v7.7-snapshot/build/linux-2.6.8-24.3-smp-i686/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/aldem/src/pike/cvs/Pike-v7.7-snapshot/build/linux-2.6.8-24.3-smp-i686/master.pike /home/aldem/src/pike/cvs/Pike-v7.7-snapshot/src/post_modules/Shuffler/make_sources.pike /home/aldem/src/pike/cvs/Pike-v7.7-snapshot/src/post_modules/Shuffler sources.h sources_to_compile [Thread debugging using libthread_db enabled] warning: Unable to set global thread event mask: generic error [New Thread -1209796032 (LWP 24314)]
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1209796032 (LWP 24314)] eval_instruction_without_debug (pc=Cannot access memory at address 0x8 ) at interpreter.h:119 119 instr = pc[0]; (gdb) bt #0 eval_instruction_without_debug (pc=Cannot access memory at address 0x8 ) at interpreter.h:119 Cannot access memory at address 0x4 (gdb) call gdb_backtraces()
THREAD_ID 0xb7e3fa40 (swapped in): /home/aldem/src/pike/cvs/Pike-v7.7-snapshot/build/linux-2.6.8-24.3-smp-i686/master.pike:2372: _main(array[8], array[57]) (gdb) --snip--
Due to some mysterious reason stack is corrupted so heavily that it cannot be used to backtrace anything... I'll try without thread support, but if this problem will disapperat then, well... No clue what to do next... I don't know Pike's internals so good to make a guess where the problem is...
Regards, /Al