Rob Deckers(deleted)
|
Backtrace from signal handler
|
Rob Deckers(deleted)
11/29/2012 9:49 AM
post97617
|
Backtrace from signal handler
I'm not sure if this is the right location, but please move it if I'm wrong.
I am developing a program on QNX Neutrino 6.4.1 and sometimes I get a signal and the program crashes.
I already have a signal handler implemented, but what I want to have is a printed back-trace in my logging.
I have read : http://www.qnx.com/developers/docs/6.4.1/neutrino/technotes/backtrace.html
and still have a few questions.
My program is multi-threaded, but I hope that the thread that enters the signal handler is the same as the one that
caused the problem, can anyone verify this?
I hope I can use "backtrace the calling thread"
In a multi-threaded application, can I use:
[code]
bt_init_accessor(&acc_sighandler1, BT_SELF);
[/code]
in the main once for ALL threads?
Or does the function needs to be called for each thread?
The function:
[code]
cnt_sighandler1 =
bt_get_backtrace(&acc_sighandler1, pc_sighandler1,
sizeof(pc_sighandler1)/sizeof(bt_addr_t));
[/code]
Gets the backtrace, but does anyone know if it delivers readable data, of function pointers?
|
|
|