Re: SIGTRAP Trace/Breakpoint Trap

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

 



On Sat, Dec 11, 2004 at 01:37:40AM +0530, Deepak V wrote:
> Hi,
> 
>   I am using insure++ to build a multi-threaded application on RED HAT
> Linux 3.2.3-37. (Linux insurertx 2.4.21-15.0.3.ELsmp #1 SMP Tue Jun 29
> 18:04:47 EDT 2004 i686 i686 i386 GNU/Linux)
> 
>   When I am running the application in GDB I am getting a SIGTRAP signal.

Insure, whatever it is, uses SIGTRAP itself:

> #0  0xb68d4f01 in kill () from /lib/tls/libc.so.6
> #1  0xb6bd1ab8 in Insure::Debug::nativeTrap () from
> /home/kodiak/ins++/lib.linux2/libinsure.so
> #2  0xb6b518d6 in Insure::Debug::trap () from
> /home/kodiak/ins++/lib.linux2/libinsure.so
> #3  0xb6b94f3a in Insure::Object::assertionFailed () from
> /home/kodiak/ins++/lib.linux2/libinsure.so

You will have to manually pass these unexpected SIGTRAPs back to your
application.

-- 
Daniel Jacobowitz


[Index of Archives]     [Linux MIPS Home]     [LKML Archive]     [Linux ARM Kernel]     [Linux ARM]     [Linux]     [Git]     [Yosemite News]     [Linux SCSI]     [Linux Hams]

  Powered by Linux