[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Libunwind-devel] Backtrace from signal handler on arm from threads
From: |
Paul Pluzhnikov |
Subject: |
Re: [Libunwind-devel] Backtrace from signal handler on arm from threads |
Date: |
Tue, 1 Feb 2011 09:55:55 -0800 |
On Tue, Feb 1, 2011 at 6:07 AM, Henrik Grindal Bakken <address@hidden> wrote:
> Does anyone have any ideas?
Run your program under gdb. When GDB stops with the intentional
SIGSEGV or SIGABRT, do "sig SIGSEGV" or "sig SIGABRT", which should
continue the program into the sigal handler, into obtain_backtrace and
into libunwind, and then GDB should stop with another crash. At that
point you'll know where this is crashing, and perhaps why. Use the
usual debugging techniques if the reason for the crash is not obvious.
Cheers,
--
Paul Pluzhnikov
- [Libunwind-devel] Backtrace from signal handler on arm from threads, Henrik Grindal Bakken, 2011/02/01
- Re: [Libunwind-devel] Backtrace from signal handler on arm from threads, Lassi Tuura, 2011/02/02
- Message not available
- Re: [Libunwind-devel] Backtrace from signal handler on arm from threads, Lassi Tuura, 2011/02/03
- [Libunwind-devel] Re: Backtrace from signal handler on arm from threads, Henrik Grindal Bakken, 2011/02/03
- Re: [Libunwind-devel] Re: Backtrace from signal handler on arm from threads, Lassi Tuura, 2011/02/03
- [Libunwind-devel] Re: Backtrace from signal handler on arm from threads, Henrik Grindal Bakken, 2011/02/03
- [Libunwind-devel] Re: Backtrace from signal handler on arm from threads, Henrik Grindal Bakken, 2011/02/03