From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7710 invoked by alias); 3 Sep 2007 02:24:23 -0000 Received: (qmail 7697 invoked by uid 22791); 3 Sep 2007 02:24:22 -0000 X-Spam-Check-By: sourceware.org Received: from mailgw.cvut.cz (HELO mailgw.cvut.cz) (147.32.3.235) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 03 Sep 2007 02:24:17 +0000 Received: from mailgw (localhost [127.0.0.1]) by mailgw.cvut.cz (Postfix) with SMTP id E5C1B13B9AC; Mon, 3 Sep 2007 04:24:14 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailgw.cvut.cz (Postfix) with ESMTP id A5FC413B9A6; Mon, 3 Sep 2007 04:24:14 +0200 (CEST) Received: from mailgw.cvut.cz ([127.0.0.1]) by localhost (mailgw [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 28613-03; Mon, 3 Sep 2007 04:24:11 +0200 (CEST) Received: from [127.0.0.1] (buk.vc.cvut.cz [147.32.240.88]) by mailgw.cvut.cz (Postfix) with ESMTP id 6763D13B7B1; Mon, 3 Sep 2007 04:24:10 +0200 (CEST) Message-ID: <46DB7048.7050309@vc.cvut.cz> Date: Mon, 03 Sep 2007 02:24:00 -0000 From: Petr Vandrovec User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.6) Gecko/20070802 Iceape/1.1.4 (Debian-1.1.4-1) MIME-Version: 1.0 To: Petr Vandrovec , ying lcs , gdb@sourceware.org Subject: Re: Program received signal SIG33, Real-time event 33. References: <568e62a40709012254j43aa5c15i9c7612350a77de55@mail.gmail.com> <46DA6B56.1060200@vc.cvut.cz> <20070902134404.GA5557@caradoc.them.org> In-Reply-To: <20070902134404.GA5557@caradoc.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-09/txt/msg00004.txt.bz2 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