From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9585 invoked by alias); 3 Apr 2007 19:47:31 -0000 Received: (qmail 9576 invoked by uid 22791); 3 Apr 2007 19:47:30 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.palmsource.com (HELO mx1.palmsource.com) (12.7.175.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 03 Apr 2007 20:47:27 +0100 Received: from localhost (localhost [127.0.0.1]) by localhost.domain.tld (Postfix) with ESMTP id CF8665F018; Tue, 3 Apr 2007 12:47:25 -0700 (PDT) Received: from mx1.palmsource.com ([127.0.0.1]) by localhost (mx1.palmsource.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 07028-03-2; Tue, 3 Apr 2007 12:47:24 -0700 (PDT) Received: from ussunex03.svl.access-company.com (ussunm001.palmsource.com [192.168.101.12]) by mx1.palmsource.com (Postfix) with ESMTP id A2B485F00A; Tue, 3 Apr 2007 12:47:24 -0700 (PDT) Received: from 192.168.92.56 ([192.168.92.56]) by ussunex03.svl.access-company.com ([192.168.101.12]) via Exchange Front-End Server owa.access-company.com ([10.0.20.19]) with Microsoft Exchange Server HTTP-DAV ; Tue, 3 Apr 2007 19:48:44 +0000 Received: from svmsnyderlnx by owa.access-company.com; 03 Apr 2007 12:47:25 -0700 Subject: RE: GDB receives SIGKILL From: Michael Snyder To: Vadim Shmelev Cc: gdb@sourceware.org In-Reply-To: <200704030712.l337CrhN031558@imap.acronis.ru> References: <200704030712.l337CrhN031558@imap.acronis.ru> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 03 Apr 2007 19:47:00 -0000 Message-Id: <1175629645.11945.11.camel@svmsnyderlnx.palmsource.com> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 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-04/txt/msg00023.txt.bz2 On Tue, 2007-04-03 at 11:15 +0400, Vadim Shmelev wrote: > Thanks for comments, Michael. Below I try to comment your comments. > > > > > (gdb) handle SIG32 nostop noprint > > Signal Stop Print Pass to program Description > > SIG32 No No Yes Real-time event 32 > > (gdb) handle SIG33 nostop noprint > > Signal Stop Print Pass to program Description > > SIG33 No No Yes Real-time event 33 > > Why did you do the above? Those signals are part of > linuxthreads handling and debugging. There should be > no need to silence them -- if there is, it could be a > sign of something wrong. > > -COMMENT------------------------------------------------------------- > If I enable SIG32 and SIG33 gdb will be stopped at every thread switch. > -END COMMENT--------------------------------------------------------- Well, this indicates that something is wrong right there. There is some mis-match between gdb, the target, and the target thread libraries. I see that you have a modern gcc (4.1.1), but an older glibc (2.3.5) and a fairly old gdb (6.3 something, circa 2004). Are you on an older Red Hat distribution, and have you perhaps added a newer gcc to it? Are you sure that your glibc is configured for old-style linux threads, and not NPTL threads? Have all of your glibc components (including libpthread and libthread_db) been configured and built together? Or have some of them been changed? What about the possibility of linking most of your libraries statically, but linking libpthread and/or libthread_db dynamically?