corrupted stack (backtrace) from sigaction handler
trafdev
trafdev at mail.ru
Thu May 5 15:32:37 UTC 2016
Looks like it's a bug of FreeBSD - wherever an error occurs, user will
see only 4 mentioned rows on a stack (using backtrace from a sigaction
handler).
In any Linux stack unwinds up to the place where error actually occurred.
More outputs appreciated before creating a bug for a FreeBSD kernel.
On 05/01/16 09:46, trafdev wrote:
> Hello!
>
> Could you launch attached code on your machine and respond with an
> output (and FreeBSD version).
>
> Here is mine (FreeBSD 10.2) output:
>
> stack dump [0] 0x40d4e5 <_Z9stackdumpPKc+0x85> at
> /ara/devel/sandbox/new/cpp/Release/cpp
> stack dump [1] 0x40dafd <_Z13signalHandleriP9__siginfoPv+0x3d> at
> /ara/devel/sandbox/new/cpp/Release/cpp
> stack dump [2] 0x801f30997 <pthread_sigmask+0x497> at /lib/libthr.so.3
> stack dump [3] 0x801f301a8 <pthread_getspecific+0xdd8> at
> /lib/libthr.so.3
>
> All info before signalHandler (foo/foo2 functions) is missed.
More information about the freebsd-hackers
mailing list