gdb arbitrarily starting threads

Ken Brown kbrown@cornell.edu
Sat Jun 20 20:42:00 GMT 2015


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 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)?

Ken

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



More information about the Cygwin mailing list