Getting stacktrace for userspace applications on crash(SIGSEGV)
danielhilst at gmail.com
Fri Sep 9 23:18:56 EDT 2016
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 <johannes at johannesthoma.com>:
> 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
> Hope that helps.
"Do or do not. There is no try"
More information about the Kernelnewbies