From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26047 invoked by alias); 4 Mar 2004 14:58:14 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 26037 invoked from network); 4 Mar 2004 14:58:12 -0000 Received: from unknown (HELO smtp.mba.ocn.ne.jp) (210.190.142.172) by sources.redhat.com with SMTP; 4 Mar 2004 14:58:12 -0000 Received: from localhost (p8186-ipad01funabasi.chiba.ocn.ne.jp [61.207.82.186]) by smtp.mba.ocn.ne.jp (Postfix) with ESMTP id 05B0653C1 for ; Thu, 4 Mar 2004 23:58:11 +0900 (JST) Date: Fri, 19 Mar 2004 00:09:00 -0000 Message-Id: <20040305.000540.59461353.anemo@mba.ocn.ne.jp> To: gdb-patches@sources.redhat.com Subject: Re: remote debugging a multi-threaded program with signal From: Atsushi Nemoto In-Reply-To: <20040304.010624.59462252.anemo@mba.ocn.ne.jp> References: <20040304.010624.59462252.anemo@mba.ocn.ne.jp> X-Fingerprint: 6ACA 1623 39BD 9A94 9B1A B746 CA77 FE94 2874 D52F X-Pgp-Public-Key: http://wwwkeys.pgp.net/pks/lookup?op=get&search=0x2874D52F Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-03/txt/msg00073.txt.bz2 >>>>> On Thu, 04 Mar 2004 01:06:24 +0900 (JST), Atsushi Nemoto said: anemo> There is a program on remote-debugging a multi-threaded program anemo> which uses signals. After receiving a signal (configured to anemo> "nostop"), the thread which receives it resumes normally but anemo> other threads leave stopped. The last packet sent to gdbserver is "$vCont;C1e:402" (see gdb.output1). gdb's info states: `vCont'[;ACTION[`:'TID]]... -- extended resume Resume the inferior. Different actions may be specified for each thread. If an action is specified with no TID, then it is applied to any threads that don't have a specific action specified; if no default action is specified then other threads should remain stopped. ... So the patcket means "continue thread 0x402 with signal 0x1e, others remain stopped". Then current gdbserver's behavior is correct. Following the info statements, gdb should send "$vCont;C1e:402;c" to handle a "nostop" signal correctly? --- Atsushi Nemoto From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26047 invoked by alias); 4 Mar 2004 14:58:14 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 26037 invoked from network); 4 Mar 2004 14:58:12 -0000 Received: from unknown (HELO smtp.mba.ocn.ne.jp) (210.190.142.172) by sources.redhat.com with SMTP; 4 Mar 2004 14:58:12 -0000 Received: from localhost (p8186-ipad01funabasi.chiba.ocn.ne.jp [61.207.82.186]) by smtp.mba.ocn.ne.jp (Postfix) with ESMTP id 05B0653C1 for ; Thu, 4 Mar 2004 23:58:11 +0900 (JST) Date: Thu, 04 Mar 2004 14:58:00 -0000 Message-ID: <20040305.000540.59461353.anemo@mba.ocn.ne.jp> To: gdb-patches@sources.redhat.com Subject: Re: remote debugging a multi-threaded program with signal From: Atsushi Nemoto In-Reply-To: <20040304.010624.59462252.anemo@mba.ocn.ne.jp> References: <20040304.010624.59462252.anemo@mba.ocn.ne.jp> X-Fingerprint: 6ACA 1623 39BD 9A94 9B1A B746 CA77 FE94 2874 D52F X-Pgp-Public-Key: http://wwwkeys.pgp.net/pks/lookup?op=get&search=0x2874D52F Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-03.o/txt/msg00073.txt Message-ID: <20040304145800.0zTZn0suI6GfpEOyCtFMLvrBZtEQhhetVRxTcxBULpE@z> >>>>> On Thu, 04 Mar 2004 01:06:24 +0900 (JST), Atsushi Nemoto said: anemo> There is a program on remote-debugging a multi-threaded program anemo> which uses signals. After receiving a signal (configured to anemo> "nostop"), the thread which receives it resumes normally but anemo> other threads leave stopped. The last packet sent to gdbserver is "$vCont;C1e:402" (see gdb.output1). gdb's info states: `vCont'[;ACTION[`:'TID]]... -- extended resume Resume the inferior. Different actions may be specified for each thread. If an action is specified with no TID, then it is applied to any threads that don't have a specific action specified; if no default action is specified then other threads should remain stopped. ... So the patcket means "continue thread 0x402 with signal 0x1e, others remain stopped". Then current gdbserver's behavior is correct. Following the info statements, gdb should send "$vCont;C1e:402;c" to handle a "nostop" signal correctly? --- Atsushi Nemoto