1. I would have the control of the process
2. I would have the backtrace stored in a variable
3. For example I would send an email with the stacktrace or print the trace
in a gui
The library works fine but end the process after a stderr print,
I think that can be very useful give a way to re-give the control
to the test.c with the backtrace throught a callback or something
like this
In any case thanks for the project it is a very good experiment
Have you considered the idea to implement the standard glibc backtrace function
on windows32? I think that it can be very usefull to many people
Original issue reported on code.google.com by
al...@paranoici.orgon 7 Dec 2010 at 12:03