From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 117069 invoked by alias); 14 Mar 2015 13:40:58 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 117052 invoked by uid 89); 14 Mar 2015 13:40:57 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Sat, 14 Mar 2015 13:40:56 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (Postfix) with ESMTPS id 3BDE48F2E1; Sat, 14 Mar 2015 13:40:55 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t2EDeqCH032247; Sat, 14 Mar 2015 09:40:53 -0400 Message-ID: <55043A63.6020103@redhat.com> Date: Sat, 14 Mar 2015 13:40:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Eli Zaretskii , gdb@sourceware.org Subject: Re: Inadvertently run inferior threads References: <83h9tq3zu3.fsf@gnu.org> In-Reply-To: <83h9tq3zu3.fsf@gnu.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2015-03/txt/msg00031.txt.bz2 On 03/12/2015 05:11 PM, Eli Zaretskii wrote: > "pp" is in this case the command that invokes an inferior function, > see src/.gdbinit in the Emacs sources for the details. Here's a handy direct url: http://git.savannah.gnu.org/cgit/emacs.git/tree/src/.gdbinit > Once this happens, the debugging session seems to be ruined: the only > thing I can do is kill the inferior and quit the debugger. Because > there doesn't seem to be any way of stopping the threads again, not on > Windows anyway. The threads are probably stopped, and GDB managed to get out of sync somehow. Otherwise, "(gdb) interrupt" would probably work. > Am I the only one who sees this annoying problem? Does anyone know > how to avoid it, or where to look for fixing it? Never seen that, but then again I don't use Windows nowadays. For run control bugs, logs are usually necessary to make sense of things. Try "set debug infrun 1" + the multiple Windows specific "set debugfoo" commands. Thanks, Pedro Alves