From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2046 invoked by alias); 6 Dec 2002 21:20:19 -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 2008 invoked from network); 6 Dec 2002 21:20:18 -0000 Received: from unknown (HELO exchange.timesys.com) (65.117.135.105) by sources.redhat.com with SMTP; 6 Dec 2002 21:20:18 -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 16:19:37 -0500 Subject: Re: Gdbserver Threading Issues From: Paul Mundt To: Daniel Jacobowitz Cc: gdb@sources.redhat.com In-Reply-To: <20021206211705.GA10918@nevyn.them.org> References: <1039206274.11722.85.camel@Origin> <20021206192849.GA4411@nevyn.them.org> <1039212714.11722.98.camel@Origin> <20021206211705.GA10918@nevyn.them.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-/Al9EVnf58xIxrhkXCmQ" Organization: TimeSys Corporation Message-Id: <1039213467.11817.102.camel@Origin> Mime-Version: 1.0 Date: Fri, 06 Dec 2002 13:20:00 -0000 X-OriginalArrivalTime: 06 Dec 2002 21:19:37.0031 (UTC) FILETIME=[2E1AF570:01C29D6D] X-SW-Source: 2002-12/txt/msg00131.txt.bz2 --=-/Al9EVnf58xIxrhkXCmQ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Content-length: 1311 On Fri, 2002-12-06 at 16:17, Daniel Jacobowitz wrote: > Thread events aren't reported immediately for latency reasons; but they > should all be delivered the first time the child stops... >=20 Even after the threads are all finished, I don't see anything stepping into handle_inferior_event() other then when the initial manager thread is created. > > Also, on the gdb side of things, it doesn't look like there are any > > events happening .. thus handle_inferior_event() is never stepped into > > at thread creation/running/exit time. Although td_thr_event_enable() > > still returns TD_OK. >=20 > Wait, what's going on? Are you saying td_thr_event_enable is being > called on your host GDB? That's not going to work right. >=20 I meant handle_inferior_event() on host gdb and td_thr_event_enable() being invoked from maybe_attach_thread() on the gdbserver side. > > Notably, if I connect gdb to gdbserver while gdb and gdbserver are both > > running under gdb control, SIG32 issues appear again..=20 >=20 > gdbserver may get a SIG32 while debugging; set the process debugging > gdbserver to "nostop noprint pass" that signal. Ditto SIG33, I think. Doing that already as a workaround, wasn't positive if this was expected or not. Regards, --=20 Paul Mundt TimeSys Corporation --=-/Al9EVnf58xIxrhkXCmQ 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 iD8DBQA98SObicEyV32UmDQRAniIAJ0Vg/wT3Zbgc775J0lndaKK3GITGgCfWPV9 HzqyDNC4ITlcpx0W/55F+ZQ= =vCmP -----END PGP SIGNATURE----- --=-/Al9EVnf58xIxrhkXCmQ--