From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20425 invoked by alias); 6 Dec 2002 22:15:58 -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 20402 invoked from network); 6 Dec 2002 22:15:50 -0000 Received: from unknown (HELO exchange.timesys.com) (65.117.135.102) by sources.redhat.com with SMTP; 6 Dec 2002 22:15:50 -0000 Received: from [192.168.2.66] ([65.117.135.98]) by exchange.timesys.com with Microsoft SMTPSVC(5.0.2195.3779); Fri, 6 Dec 2002 17:15:09 -0500 Subject: Re: Gdbserver Threading Issues From: Paul Mundt To: Daniel Jacobowitz Cc: gdb@sources.redhat.com In-Reply-To: <20021206220925.GA14064@nevyn.them.org> 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> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-y/zoGS80O4peCGULX0TG" Organization: TimeSys Corporation Message-Id: <1039216800.15470.10.camel@Origin> Mime-Version: 1.0 Date: Fri, 06 Dec 2002 14:15:00 -0000 X-OriginalArrivalTime: 06 Dec 2002 22:15:09.0343 (UTC) FILETIME=[F0516AF0:01C29D74] X-SW-Source: 2002-12/txt/msg00138.txt.bz2 --=-y/zoGS80O4peCGULX0TG Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Content-length: 1159 On Fri, 2002-12-06 at 17:09, Daniel Jacobowitz wrote: > > The log with remote debugging turned on is attached.. >=20 > 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. 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. Regards, --=20 Paul Mundt TimeSys Corporation --=-y/zoGS80O4peCGULX0TG Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part Content-length: 232 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA98TCgicEyV32UmDQRAol0AKCB1mTLh92qjKG4jSqV3ii9aB0qCwCg5k9O BcOULzepsVwLkOOS3Ydyoyk= =JAy6 -----END PGP SIGNATURE----- --=-y/zoGS80O4peCGULX0TG--