From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16058 invoked by alias); 23 Jun 2003 19:49:46 -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 16000 invoked from network); 23 Jun 2003 19:49:45 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 23 Jun 2003 19:49:45 -0000 Received: from dsl093-172-017.pit1.dsl.speakeasy.net ([66.93.172.17] helo=nevyn.them.org ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 19UXKj-0004zg-00; Mon, 23 Jun 2003 14:50:33 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19UXJo-00035K-00; Mon, 23 Jun 2003 15:49:36 -0400 Date: Mon, 23 Jun 2003 19:49:00 -0000 From: Daniel Jacobowitz To: nak26 Cc: gdb@sources.redhat.com Subject: Re: gdbserver multithreaded debugging problem Message-ID: <20030623194935.GA11083@nevyn.them.org> Mail-Followup-To: nak26 , gdb@sources.redhat.com References: <3EF77554@webmail.drexel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EF77554@webmail.drexel.edu> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-06/txt/msg00462.txt.bz2 On Mon, Jun 23, 2003 at 03:39:06PM -0400, nak26 wrote: > Hi: > > I am trying to use gdbserver to remotely debug a multithreaded application. > > Remote host is a IA32, running MontaVista Linux 3.0 kernel v 2.4.18; gdbserver > from the 5.3 release tarball, patched with the PREPARE_TO_PROCEED patch, and > built on the remote host. > > Local host is an IA32 machine, running RedHat 8.0, gdb v 5.2.1-4. > > I get a "Real-time event 32"-signal as each thread is spun up, execution > stops, and I have to re-continue. After all the threads are created and I hit > a breakpoint, info thread only displays the main thread. > > I don't see this problem while debugging with gdb (5.2.1) on the remote (and > the local) target > . > Is there anything I can do to solve the problem I am experiencing with > gdbserver? Did gdbserver detect thread support when you built it? Check the output of configure. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer