This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: SIGSEGV in loaded shared library
- From: Daniel Jacobowitz <drow at false dot org>
- To: gdb at sources dot redhat dot com
- Date: Mon, 12 Mar 2007 22:45:30 -0400
- Subject: Re: SIGSEGV in loaded shared library
- References: <20070313023828.GA29896@cox.net>
On Mon, Mar 12, 2007 at 10:38:28PM -0400, Bob Rossi wrote:
> Hi,
>
> I have a situation where I'm loading a shared library into memory with
> dlopen. Then the library crashes with a SIGSEGV because it's doing
> something wrong. When I run the program under GDB, it doesn't seem to
> catch the SIGSEGV the same way it would if the crash happened in the
> main application. Instead of GDB giving me a backtrace to the SIGSEGV,
> it seems as if an exception is thrown. Is there a way to have GDB give
> me the backtrace like it would if the SIGSEGV was in the main
> application?
>
> Is this known behavior or is it possible I'm doing something wrong?
That doesn't sound at all likely, so it's probable that something else
is going on you haven't explained or realized. It shouldn't matter
where the signal is raised.
--
Daniel Jacobowitz
CodeSourcery