From: Daniel Jacobowitz <dan@debian.org>
To: Deepak V <vdeepak79@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: SIGTRAP Trace/Breakpoint Trap
Date: Fri, 10 Dec 2004 15:55:53 -0500 [thread overview]
Message-ID: <20041210205553.GA19358@nevyn.them.org> (raw)
In-Reply-To: <842f1e5f04121012074f6ddff0@mail.gmail.com>
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
prev parent reply other threads:[~2004-12-10 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 20:07 SIGTRAP Trace/Breakpoint Trap Deepak V
2004-12-10 20:55 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041210205553.GA19358@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=vdeepak79@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.