From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31849 invoked by alias); 6 Dec 2002 21:16:29 -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 31839 invoked from network); 6 Dec 2002 21:16:28 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 6 Dec 2002 21:16:28 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18KRi8-0001o0-00; Fri, 06 Dec 2002 17:16:45 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18KPqL-0002sn-00; Fri, 06 Dec 2002 16:17:05 -0500 Date: Fri, 06 Dec 2002 13:16:00 -0000 From: Daniel Jacobowitz To: Paul Mundt Cc: gdb@sources.redhat.com Subject: Re: Gdbserver Threading Issues Message-ID: <20021206211705.GA10918@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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1039212714.11722.98.camel@Origin> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-12/txt/msg00130.txt.bz2 On Fri, Dec 06, 2002 at 05:11:54PM -0500, Paul Mundt wrote: > On Fri, 2002-12-06 at 14:28, Daniel Jacobowitz wrote: > > Not without more information. Look at the remote session transcript, > > see what is going on. > > Hum, still debugging this .. I'm still at a loss as to why breakpoints > would be having any effect on anything, though from the looks of it the > newly created threads are tracked just fine by > thread_db_find_new_threads() in gdbserver/thread-db.c > > Also single stepping through maybe_attach_thread() everything looks > alright, though still the threads don't show up on the GDB side. Thread events aren't reported immediately for latency reasons; but they should all be delivered the first time the child stops... > 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. 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. > Notably, if I connect gdb to gdbserver while gdb and gdbserver are both > running under gdb control, SIG32 issues appear again.. gdbserver may get a SIG32 while debugging; set the process debugging gdbserver to "nostop noprint pass" that signal. Ditto SIG33, I think. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer