From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17543 invoked by alias); 28 Jun 2003 20:02:12 -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 17536 invoked from network); 28 Jun 2003 20:02:12 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 28 Jun 2003 20:02:12 -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 19WLuc-0007MK-00; Sat, 28 Jun 2003 15:03:07 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19WLtP-0006wv-00; Sat, 28 Jun 2003 16:01:51 -0400 Date: Sat, 28 Jun 2003 20:29: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: <20030628200150.GA26696@nevyn.them.org> Mail-Followup-To: Jon Ringle , gdb@sources.redhat.com References: <200306280128.02056.jon.ringle@comdial.com> <200306281101.34861.jon.ringle@comdial.com> <20030628152137.GB8004@nevyn.them.org> <200306281311.06525.jon.ringle@comdial.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200306281311.06525.jon.ringle@comdial.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-06/txt/msg00530.txt.bz2 On Sat, Jun 28, 2003 at 01:11:06PM -0400, Jon Ringle wrote: > > > 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... > > I turned on remote_debug = 1, and debug_threads = 1 on gdbserver, and I get > the following on the target when I continue. The signal 32 looks suspect to > me. It is correct. The thread manager uses that. What are you running on the ARM board? What's the rest of the gdbserver log? > getpkt ("c"); [sending ack] > [sent ack] > Resuming process 179 (continue, signal 0, stop not expected) > Checking for breakpoint. > Removed breakpoint. > Got an event from 179 (57f) > Hit a (non-reinsert) breakpoint. > Thread creation event. > Writing 00 to 40111a2c > Attaching to thread 2049 (LWP 194) > Writing 01 to 40111a28 > Writing 0d to 40104d44 > Resuming process 179 (step, signal 0, stop not expected) > pending reinsert at 40104d44Checking for breakpoint. > Removed breakpoint. > Got an event from 194 (137f) > Expected stop. > Resuming process 194 (continue, signal 0, stop not expected) > Ignored signal 32 for 1024 (LWP 179). > Resuming process 179 (step, signal 32, stop not expected) > pending reinsert at 40104d44 > -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer