How about dumping C backtraces also, when possible (probably limited to Linux?).
That'd be very welcome. I've missed it many times when trying to debug heavy production systems.
/ Martin Stjernholm, Roxen IS
Previous text:
2003-10-02 17:18: Subject: Some tasks from the conference
o Add local_install target to the module make system, to make it simple for users who download standalone modules to get them installed in their user account instead of in the system pike installation.
Perhaps a ~/.pikerc with some settings in it such as extra module paths would be nice too? Simple enough to fix at least.
o Dump pike backtraces on SIGSEGV.
How about dumping C backtraces also, when possible (probably limited to Linux?). I have code for this and it would be, especially combined with pike backtraces, quite useful in case you get sporadic crashes and can't always run with gdb. Example output:
Signal SIGQUIT received.
Stack dump: { ./hdb(print_backtrace+0x1d) [0x8063429] /lib/libpthread.so.0 [0x4fc3bfea] /lib/libc.so.6 [0x4f9f6288] ./hdb(main+0x30d) [0x809216d] /lib/libc.so.6(__libc_start_main+0xc7) [0x4f9e27a7] ./hdb(XMapRaised+0x39) [0x80624e1] }
Naturally the above happens at a stage where only main has been called so it's not so interesting. The addresses are easily used in gcc with `info line *ADDR' or with the addr2line command line tool (which doesn't handle dynamically loaded modules though).
/ David Hedbor