Re: Getting stacktrace for userspace applications on crash(SIGSEGV)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxx>:
> 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

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux