From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30510 invoked by alias); 28 Jun 2003 15:21:40 -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 30503 invoked from network); 28 Jun 2003 15:21:40 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 28 Jun 2003 15:21:40 -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 19WHX9-0006w0-00; Sat, 28 Jun 2003 10:22:35 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19WHWD-00026A-00; Sat, 28 Jun 2003 11:21:37 -0400 Date: Sat, 28 Jun 2003 15:30:00 -0000 From: Daniel Jacobowitz To: Jon Ringle Cc: gdb@sources.redhat.com Subject: Re: pthread_create does not return when remote debugging Message-ID: <20030628152137.GB8004@nevyn.them.org> Mail-Followup-To: Jon Ringle , gdb@sources.redhat.com References: <200306280128.02056.jon.ringle@comdial.com> <20030628144324.GA7298@nevyn.them.org> <200306281101.34861.jon.ringle@comdial.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200306281101.34861.jon.ringle@comdial.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-06/txt/msg00526.txt.bz2 On Sat, Jun 28, 2003 at 11:01:34AM -0400, Jon Ringle wrote: > On Saturday 28 June 2003 10:43 am, Daniel Jacobowitz wrote: > > On Sat, Jun 28, 2003 at 01:28:02AM -0400, Jon Ringle wrote: > > > Hi, > > > > > > I am having an issue when remote debugging a multi-threaded app, a call > > > to pthread_create hangs inside __pthread_wait_for_restart_signal on the > > > host gdb. > > > > Have you tried this without the breakpoint in pthread_create? > > I have. This is what I had initially done, and narrow the problem down to > pthread_create never returning. > > > > > Other than that nothing obvious comes to mind, you'll have to > > investigate yourself. Sorry. > > Could the problem be on the gdbserver side not sending back anything in > response to gdb Sending packet: &c#63...Ack? No. That's a continue request. The target isn't stopping again, but that's not gdbserver's fault... it won't respond to the client until the program stops. Find out why it's not stopping... -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer