Thanks for the help Jon :) A core was dumped (couldn't be attached because it bounced back) and I tried gdb. The output was:
(gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0x4005091b in raise () from /tools/lib/libc.so.6 #2 0x40051e1e in abort () from /tools/lib/libc.so.6 #3 0x00000041 in ?? () #4 0x40150120 in ?? () from /tools/lib/libc.so.6 #5 0x400901d0 in realloc () from /tools/lib/libc.so.6 #6 0x08239c48 in ?? () #7 0x00000068 in ?? () #8 0x08239c50 in ?? () #9 0x4014eff4 in ?? () from /tools/lib/libc.so.6 #10 0x00000041 in ?? () #11 0x08239c50 in ?? () #12 0x00000040 in ?? () #13 0x400846ed in vasprintf () from /tools/lib/libc.so.6 #14 0x00000000 in ?? () I hope this helps. Best regards, Alex > Do you mean you have never worked with a debugger? > > I'm not certain, but that assertion should then call abort(), which > means a core file will be dumped. (Just do ulimit -c 50000 in your > shell before you run make, to be sure core files are not disabled on > your distro). > > then you can do gdb -c core.xxx -se /path/to/make > > then "bt" to get the backtrace of the assert. > > Cheers, Jon _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 _______________________________________________ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make