From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-44201-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 99450 invoked by alias); 14 Mar 2015 14:56:11 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Received: (qmail 99439 invoked by uid 89); 14 Mar 2015 14:56:10 -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,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: mtaout22.012.net.il
Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 14 Mar 2015 14:56:08 +0000
Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0NL700I00IGDH800@a-mtaout22.012.net.il> for gdb@sourceware.org; Sat, 14 Mar 2015 16:56:05 +0200 (IST)
Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NL700IM1ITGD370@a-mtaout22.012.net.il>; Sat, 14 Mar 2015 16:56:04 +0200 (IST)
Date: Sat, 14 Mar 2015 14:56:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Inadvertently run inferior threads
In-reply-to: <55043A63.6020103@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <8361a339xd.fsf@gnu.org>
References: <83h9tq3zu3.fsf@gnu.org> <55043A63.6020103@redhat.com>
X-IsSubscribed: yes
X-SW-Source: 2015-03/txt/msg00032.txt.bz2

> Date: Sat, 14 Mar 2015 13:40:51 +0000
> From: Pedro Alves <palves@redhat.com>
> 
> > 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.

In that case, the cause of it getting out of sync is the new thread
that was started (probably by Windows)?

> Otherwise, "(gdb) interrupt" would probably work.

Thanks, I will try using this next time.

> 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.

OK, will try that as well.  Thanks.