From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-29502-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 29916 invoked by alias); 3 Sep 2007 03:07:06 -0000
Received: (qmail 29779 invoked by uid 22791); 3 Sep 2007 03:07:05 -0000
X-Spam-Check-By: sourceware.org
Received: from rv-out-0910.google.com (HELO rv-out-0910.google.com) (209.85.198.186)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 03 Sep 2007 03:06:58 +0000
Received: by rv-out-0910.google.com with SMTP id l15so728258rvb         for <gdb@sourceware.org>; Sun, 02 Sep 2007 20:06:56 -0700 (PDT)
Received: by 10.142.252.11 with SMTP id z11mr207053wfh.1188788816388;         Sun, 02 Sep 2007 20:06:56 -0700 (PDT)
Received: by 10.142.253.7 with HTTP; Sun, 2 Sep 2007 20:06:56 -0700 (PDT)
Message-ID: <568e62a40709022006n3ebf3b14s2a20b71e684e07ac@mail.gmail.com>
Date: Mon, 03 Sep 2007 03:07:00 -0000
From: "ying lcs" <yinglcs@gmail.com>
To: "Petr Vandrovec" <vandrove@vc.cvut.cz>
Subject: Re: Program received signal SIG33, Real-time event 33.
Cc: gdb@sourceware.org
In-Reply-To: <46DB7048.7050309@vc.cvut.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <568e62a40709012254j43aa5c15i9c7612350a77de55@mail.gmail.com> 	 <46DA6B56.1060200@vc.cvut.cz> <20070902134404.GA5557@caradoc.them.org> 	 <46DB7048.7050309@vc.cvut.cz>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2007-09/txt/msg00005.txt.bz2

On 9/2/07, Petr Vandrovec <vandrove@vc.cvut.cz> wrote:
> 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
>

I am trying to run Darwin (apple's open source streaming server) in
gdb on Fedora 5.  I am not sure if it uses setuid().

What should I do? upgrade to newer gdb? or glibc?
>
>