From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: gdb arbitrarily starting threads
Date: Sat, 20 Jun 2015 20:42:00 -0000 [thread overview]
Message-ID: <5585D052.2010009@cornell.edu> (raw)
In-Reply-To: <CAH5rLZXbYNUwB_f2Vigev--NsmB3FrdhWre1uYxAr0ckN8NvmQ@mail.gmail.com>
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
next prev parent reply other threads:[~2015-06-20 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 13:29 William M. (Mike) Miller
2015-06-20 18:47 ` Corinna Vinschen
2015-06-20 20:02 ` William M. (Mike) Miller
2015-06-20 20:42 ` Ken Brown [this message]
2015-06-20 20:51 ` William M. (Mike) Miller
2015-06-21 19:29 ` Ken Brown
2015-06-22 0:28 ` William M. (Mike) Miller
2015-06-24 14:33 ` Eli Zaretskii
2015-09-05 17:16 ` William M. (Mike) Miller
2015-09-13 15:21 ` William M. (Mike) Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5585D052.2010009@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).