From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Petr Vandrovec <vandrove@vc.cvut.cz>,
ying lcs <yinglcs@gmail.com>,
gdb@sourceware.org
Subject: Re: Program received signal SIG33, Real-time event 33.
Date: Mon, 03 Sep 2007 02:24:00 -0000 [thread overview]
Message-ID: <46DB7048.7050309@vc.cvut.cz> (raw)
In-Reply-To: <20070902134404.GA5557@caradoc.them.org>
Daniel Jacobowitz wrote:
> 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.
If Ying uses setuid() from multithreaded program then I think that glibc
has more than one surprise ready for him...
Petr
next prev parent reply other threads:[~2007-09-03 2:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 5:54 ying lcs
2007-09-02 7:50 ` Petr Vandrovec
2007-09-02 13:44 ` Daniel Jacobowitz
2007-09-03 2:24 ` Petr Vandrovec [this message]
2007-09-03 3:07 ` ying lcs
2007-09-03 7:47 ` Mark Kettenis
2007-09-03 8:04 ` Petr Vandrovec
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=46DB7048.7050309@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=gdb@sourceware.org \
--cc=yinglcs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox