From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27788 invoked by alias); 4 Dec 2002 18:44:56 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 27781 invoked from network); 4 Dec 2002 18:44:55 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 4 Dec 2002 18:44:55 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18JgOX-00081g-00; Wed, 04 Dec 2002 14:45:21 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18JeWU-0006jE-00; Wed, 04 Dec 2002 13:45:26 -0500 Date: Wed, 04 Dec 2002 10:44:00 -0000 From: Daniel Jacobowitz To: Paul Mundt Cc: gdb@sources.redhat.com Subject: Re: SIG32/SIGTRAP issues Message-ID: <20021204184526.GA25681@nevyn.them.org> Mail-Followup-To: Paul Mundt , gdb@sources.redhat.com References: <1038959780.11721.54.camel@Origin> <20021203232457.GA5980@nevyn.them.org> <1039030436.11722.76.camel@Origin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1039030436.11722.76.camel@Origin> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-12/txt/msg00079.txt.bz2 On Wed, Dec 04, 2002 at 02:33:57PM -0500, Paul Mundt wrote: > Hi, > > On Tue, 2002-12-03 at 18:24, Daniel Jacobowitz wrote: > > Funny, no one reports this for months and this is the third report I've > > seen in a week... At the bottom of this message is a workaround. I'm > > not proposing it be committed, since it's obviously pretty gross. The > > real issue is the concept of thread_stratum and core_stratum as > > separate from process_stratum. I don't think it's appropriate - if we > > are debugging a core and process at the same time this isn't how it > > should work. This ties in to all the make-targets-a-real-stack thing - > > I'm not entirely convinced on that score either. > > Okay, making progress. This takes care of the SIG32/SIGTRAP issues, > though now it looks like PPC is stuck on SIG33 issues. > > Running the same test-case from yesterday, if I run the shared version > twice in a row, gdb segfaults. If I run the shared or static version of > the app under gdb under gdb, I get SIG33 (which occurs in different > locations per-thread if its static). SIG33 is CANCEL. Lin-lwp should be reporting it as such. Do you have __pthread_sig_cancel in your library? Is check_thread_signals working? > (top-gdb) bt > Reading in symbols for ../../package/gdb/dbxread.c...done. > Reading in symbols for ../../package/gdb/elfread.c... and > ../../package/gdb/solib-svr4.c...done. > Reading in symbols for ../../package/gdb/solib.c...done. > #0 0x0fe04b08 in strchr () from /lib/libc.so.6 > #1 0x1010597c in end_psymtab (pst=0x106f5ea0, include_list=0x7fffe910, > num_includes=1, capping_symbol_offset=-16843009, > capping_text=2139062143, > dependency_list=0x7fffe880, number_dependencies=0, > textlow_not_set=1) at ../../package/gdb/dbxread.c:2253 > #2 0x10104a40 in read_dbx_symtab (objfile=0x104e4a88) at > ../../package/gdb/dbxread.c:1524 Dunno about this one, try a newer GDB maybe. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer