From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18319 invoked by alias); 7 Dec 2002 01:15:11 -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 18307 invoked from network); 7 Dec 2002 01:15:10 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 7 Dec 2002 01:15:10 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18KVR9-0002CI-00; Fri, 06 Dec 2002 21:15:27 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18KTZL-0005YX-00; Fri, 06 Dec 2002 20:15:47 -0500 Date: Fri, 06 Dec 2002 17:15:00 -0000 From: Daniel Jacobowitz To: Paul Mundt Cc: gdb@sources.redhat.com Subject: Re: Gdbserver Threading Issues Message-ID: <20021207011547.GA21192@nevyn.them.org> Mail-Followup-To: Paul Mundt , gdb@sources.redhat.com References: <1039206274.11722.85.camel@Origin> <20021206192849.GA4411@nevyn.them.org> <1039212714.11722.98.camel@Origin> <20021206211705.GA10918@nevyn.them.org> <1039213467.11817.102.camel@Origin> <20021206212311.GA11304@nevyn.them.org> <1039215818.15473.3.camel@Origin> <20021206220925.GA14064@nevyn.them.org> <1039216800.15470.10.camel@Origin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1039216800.15470.10.camel@Origin> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-12/txt/msg00146.txt.bz2 On Fri, Dec 06, 2002 at 06:20:00PM -0500, Paul Mundt wrote: > On Fri, 2002-12-06 at 17:09, Daniel Jacobowitz wrote: > > > The log with remote debugging turned on is attached.. > > > > So: what are you doing in GDB to get this log; what is happening; what > > do you expect to happen? I don't see an obvious problem. > > Same thing as what I explained in my intial post. > > The test app starts up and spawns some arbitrary number of threads, > which in turn sleep for a bit and then return.. in this case, 2 threads. > > When running this test app under gdbserver, the only thread being > reported to gdb is the manager thread.. (ie, [New thread x (LWP y)]). > > Because of this, I can't do 'info threads' and see anything other then > the manager thread .. and thus can't really do any thread-specific > debugging. Actually it's the _initial_ thread, not the manager thread, most likely. > If I run natively, this isn't an issue. > > If I insert a breakpoint in the function being run by the threads, then > everything comes up fine. Then I can break after the threads are created > and do per-thread debugging without any issues.. but only if I place a > breakpoint there. > > If this isn't clear enough, I can toss together a brief log of what I'm > doing. You won't get [New thread x (LWP y)] messages at thread creation time if you're using gdbserver; you'll get them when you stop for some other reason and do info threads, generally. If you never stop the running application you won't see them. But are you stopping the application some other way and not having threads show up? A precise example session would be appreciated. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer