This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Program received signal SIG33, Real-time event 33.

From: Daniel Jacobowitz <drow at false dot org>
To: Petr Vandrovec <vandrove at vc dot cvut dot cz>
Cc: ying lcs <yinglcs at gmail dot com>, gdb at sourceware dot org
Date: Sun, 2 Sep 2007 09:44:05 -0400
Subject: Re: Program received signal SIG33, Real-time event 33.
References: <568e62a40709012254j43aa5c15i9c7612350a77de55@mail.gmail.com> <46DA6B56.1060200@vc.cvut.cz>

On Sun, Sep 02, 2007 at 12:50:46AM -0700, Petr Vandrovec wrote:
> Apparently your program uses signals...  If this is expected (which probably is 
> for realtime signals) then
> 
> handle SIG33 nostop noprint pass
> 
> will configure gdb so this signal is ignored by gdb, but delivered to program 
> like without gdb.

No, SIG33 is generally internal to the threading implementation.

GDB 6.3 is somewhat old.  I recommend trying a current version.

-- 
Daniel Jacobowitz
CodeSourcery

Follow-Ups:
- Re: Program received signal SIG33, Real-time event 33.
  - From: Petr Vandrovec

References:
- Program received signal SIG33, Real-time event 33.
  - From: ying lcs
- Re: Program received signal SIG33, Real-time event 33.
  - From: Petr Vandrovec

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]