From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23523 invoked by alias); 6 Mar 2004 12:42:31 -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 23515 invoked from network); 6 Mar 2004 12:42:28 -0000 Received: from unknown (HELO smtp.mba.ocn.ne.jp) (210.190.142.172) by sources.redhat.com with SMTP; 6 Mar 2004 12:42:28 -0000 Received: from localhost (p5133-ipad27funabasi.chiba.ocn.ne.jp [220.107.196.133]) by smtp.mba.ocn.ne.jp (Postfix) with ESMTP id E401D5AF6; Sat, 6 Mar 2004 21:42:25 +0900 (JST) Date: Sat, 06 Mar 2004 12:42:00 -0000 Message-Id: <20040306.215001.74755311.anemo@mba.ocn.ne.jp> To: drow@false.org Cc: gdb-patches@sources.redhat.com Subject: Re: remote debugging a multi-threaded program with signal From: Atsushi Nemoto In-Reply-To: <20040305163854.GA23778@nevyn.them.org> References: <20040305.112722.74754522.nemoto@toshiba-tops.co.jp> <20040306.014343.74756819.anemo@mba.ocn.ne.jp> <20040305163854.GA23778@nevyn.them.org> 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/msg00123.txt >>>>> On Fri, 5 Mar 2004 11:38:54 -0500, Daniel Jacobowitz said: >> For gdb without verbose-resume, how about this patch? With this >> patch, gdbserver uses general_thread instead of all_threads.head if >> 'CNN' packet was sent without preceding 'HcNN'. drow> For one thing, I'm not sure it will work. But for another, why drow> is this case important to you? It solves at least my program case, and I believe it breaks nothing. I'm still sometimes using (slightly patched) gdb 5.3. If I can solve the problem with verbose-resume disabled in current gdb, I suppose the fixes can be backported to gdb 5.3 easily. I already tried your fix of infrun.c with gdb 5.3 and found it solves a part of problem. drow> Without vCont the problem is fundamentally insoluble; there will drow> always be a case in which gdbserver mis-guesses which thread it drow> should continue. That's why I had to come up with a protocol drow> change. Hmm... then it might be better to backport all vCont stuff? Of course upgrading to upcoming gdb 6.1 will be the best solution, but I can not for now by some internal reason ... :-\ --- Atsushi Nemoto From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23523 invoked by alias); 6 Mar 2004 12:42:31 -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 23515 invoked from network); 6 Mar 2004 12:42:28 -0000 Received: from unknown (HELO smtp.mba.ocn.ne.jp) (210.190.142.172) by sources.redhat.com with SMTP; 6 Mar 2004 12:42:28 -0000 Received: from localhost (p5133-ipad27funabasi.chiba.ocn.ne.jp [220.107.196.133]) by smtp.mba.ocn.ne.jp (Postfix) with ESMTP id E401D5AF6; Sat, 6 Mar 2004 21:42:25 +0900 (JST) Date: Fri, 19 Mar 2004 00:09:00 -0000 Message-ID: <20040306.215001.74755311.anemo@mba.ocn.ne.jp> To: drow@false.org Cc: gdb-patches@sources.redhat.com Subject: Re: remote debugging a multi-threaded program with signal From: Atsushi Nemoto In-Reply-To: <20040305163854.GA23778@nevyn.them.org> References: <20040305.112722.74754522.nemoto@toshiba-tops.co.jp> <20040306.014343.74756819.anemo@mba.ocn.ne.jp> <20040305163854.GA23778@nevyn.them.org> 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/msg00123.txt.bz2 Message-ID: <20040319000900.pphddFJyEAN4F43V-26qzBzhSoSz552XK4Nlm9T2GKU@z> >>>>> On Fri, 5 Mar 2004 11:38:54 -0500, Daniel Jacobowitz said: >> For gdb without verbose-resume, how about this patch? With this >> patch, gdbserver uses general_thread instead of all_threads.head if >> 'CNN' packet was sent without preceding 'HcNN'. drow> For one thing, I'm not sure it will work. But for another, why drow> is this case important to you? It solves at least my program case, and I believe it breaks nothing. I'm still sometimes using (slightly patched) gdb 5.3. If I can solve the problem with verbose-resume disabled in current gdb, I suppose the fixes can be backported to gdb 5.3 easily. I already tried your fix of infrun.c with gdb 5.3 and found it solves a part of problem. drow> Without vCont the problem is fundamentally insoluble; there will drow> always be a case in which gdbserver mis-guesses which thread it drow> should continue. That's why I had to come up with a protocol drow> change. Hmm... then it might be better to backport all vCont stuff? Of course upgrading to upcoming gdb 6.1 will be the best solution, but I can not for now by some internal reason ... :-\ --- Atsushi Nemoto