This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: gdb arbitrarily starting threads
- From: "William M. (Mike) Miller" <william dot m dot miller at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 20 Jun 2015 16:51:33 -0400
- Subject: Re: gdb arbitrarily starting threads
- Authentication-results: sourceware.org; auth=none
- References: <CAH5rLZVsTzSVTRzG_Aucw=_i-o5M-G0_ddPu0gPaqQM-Nn3iJg at mail dot gmail dot com> <20150620184715 dot GA17350 at calimero dot vinschen dot de> <CAH5rLZXbYNUwB_f2Vigev--NsmB3FrdhWre1uYxAr0ckN8NvmQ at mail dot gmail dot com> <5585D052 dot 2010009 at cornell dot edu>
On Sat, Jun 20, 2015 at 4:42 PM, Ken Brown <kbrown@cornell.edu> wrote:
> On 6/20/2015 4:02 PM, William M. (Mike) Miller wrote:
>>
>> Thanks for the reply. My concern, however, isn't that new threads are
>> being created; it's that when gdb does this, it sets the state of all
>> threads, including my main thread, to "(running)" so that I can't
>> single-step through my program any more. If I try to say "next", I
>> get the error:
>>
>> Cannot execute this command while the selected thread is running.
>>
>> But I did nothing overt to start my thread.
>>
>> It never used to do this, but it happens regularly now.
>
>
> I'm not seeing this on my system (Windows 7, both 32-bit and 64-bit Cygwin).
I'm running 8.1, so that could well be the difference there.
> I debugged the emacs source, set a breakpoint, and stepped through the
> program when the breakpoint was hit.
>
> Could this be caused by BLODA interference
> (https://cygwin.com/faq/faq.html#faq.using.bloda)?
I certainly won't say that it's impossible, but I think it's unlikely.
The symptoms mentioned there don't seem related. Also, the only one
of those programs I'm using is Windows Defender, and I've been using
it for over two years, but this problem only started within the last
few months. (Of course, I suppose it's possible that something in
Cygwin/gdb/gcc changed to make it more sensitive, or an update to
Windows Defender made it more intrusive...)
Failing a way to keep gdb from doing this, is there a way in gdb to
stop a thread that's in "(running)" state? (Even though it's sitting
at a breakpoint.)
--
William M. (Mike) Miller | Edison Design Group
william.m.miller@gmail.com
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple