AW: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 <johannes@johannesthoma.com>:
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
Hi, Am 10.09.16 um 05:18 schrieb Daniel.:
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? AFAIK a signal (like SIGSEGV) is always sent to the whole process not to a specific thread. Therefore gdb cannot know which thread caused the segfault (except if it would analyse the assembly which it doesn't). So, unfortunately you'll have to find the misbehaving thread by yourself ..
Best, - Johannes
Thanks for the help and best regards!!! ;)
Ohhh, I see, Thansk Johannes, now everything make sense. If this was a post I would mark it as SOLVED :) Best regards, 2016-09-11 14:39 GMT-03:00 Johannes Thoma <johannes@johannesthoma.com>:
Hi,
Am 10.09.16 um 05:18 schrieb Daniel.:
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?
AFAIK a signal (like SIGSEGV) is always sent to the whole process not to a specific thread. Therefore gdb cannot know which thread caused the segfault (except if it would analyse the assembly which it doesn't). So, unfortunately you'll have to find the misbehaving thread by yourself ..
Best,
- Johannes
Thanks for the help and best regards!!!
;)
-- "Do or do not. There is no try" Yoda Master
participants (2)
-
Daniel. -
Johannes Thoma