From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11544 invoked by alias); 28 Jun 2006 02:34:47 -0000 Received: (qmail 11535 invoked by uid 22791); 28 Jun 2006 02:34:47 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 28 Jun 2006 02:34:45 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FvPt2-0007nW-Ui; Tue, 27 Jun 2006 22:34:41 -0400 Date: Thu, 29 Jun 2006 15:14:00 -0000 From: Daniel Jacobowitz To: "Steven J. Hill" Cc: "FALE(Leopold Faschalek)" , gdb@sourceware.org Subject: Re: Linux threads and insight 6.4 / 6.5 Message-ID: <20060628023440.GA29935@nevyn.them.org> Mail-Followup-To: "Steven J. Hill" , "FALE(Leopold Faschalek)" , gdb@sourceware.org References: <44A1CCC5.1090606@realitydiluted.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44A1CCC5.1090606@realitydiluted.com> User-Agent: Mutt/1.5.11+cvs20060403 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00258.txt.bz2 On Tue, Jun 27, 2006 at 07:26:45PM -0500, Steven J. Hill wrote: > FALE(Leopold Faschalek) wrote: > > > > The thread model is linuxthreads (not NPTL). > > > > ================== target ====================== > > /img # ./gdbserver64 192.168.184.10:5000 ./test > > Process ./test created; pid = 370 > > Listening on port 5000 > > Remote debugging from host 192.168.184.10 > > > > Child terminated with signal = 9 > > > > Child terminated with signal = 0x9 > > GDBserver exiting Sorry, I didn't respond to this because I don't know what could cause it. You might want to search the archives for problems with thread debugging; the usual suspects are library mismatches. > That's okay. I'm using NPTL on MIPS with the latest gdbserver (6.5) and > it does the exact same thing for me, kind of. Mine exits with signal 5. > As usual, threads support is iffy. With signal 5 is a clear signal that gdbserver has not enabled thread support, either because of a mismatch or a problem with libthread_db support on your target. When one thread hits a breakpoint, if another thread is running outside of debugger control, the kernel may terminate the entire process. -- Daniel Jacobowitz CodeSourcery