Getting stacktrace for userspace applications on crash(SIGSEGV)

Yeap it is. The protocol takes 4 threads the other are user's threads.
Still, when getting some core dump and fatal error log I was expecting
to get backtrace from the thread responsible for the segmentation
fault? Am I wrong?

Thanks for the help and best regards!!!

2016-09-09 18:42 GMT-03:00 Johannes Thoma [off-list ref]:

Hi,

Is it a multi threading application? Type

info threads

in gdb to find out. With

thread threadnum

you can switch between threads and then display the other backtraces with

bt

Hope that helps.

Best

Johannes

-- 
"Do or do not. There is no try"
  Yoda Master