------- Comment #4 from fxcoudert at gcc dot gnu dot org 2006-10-31 16:01 ------- (In reply to comment #3) > coredumping is easy, simply call "abort()" or kill(0,SIGSEGV)"
The usual signal to request a core dump is SIGQUIT. > However, I'm more a fan of either coredumping Same opinion here. > (or, if someone wants to spend the time, of creating a real strack-tracing > function as the comercial compilers [and gdb] have). Using unwind is the way to go for a more serious solution. It's how java does it, for example (with addr2line to get file and line information). I had it working on x86 at some point: http://www.eleves.ens.fr/home/coudert/unwind.diff I think it's a good point for someone trying to work on that. -- fxcoudert at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2006-10-30 12:24:41 |2006-10-31 16:01:05 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29649
