public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/18127] threads spawned by infcall end up stuck in "running" state
Date: Tue, 05 May 2015 17:07:00 -0000	[thread overview]
Message-ID: <bug-18127-4717-iLJ7V5dGxK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18127-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18127

--- Comment #2 from Pedro Alves <palves at redhat dot com> ---
Thanks.   

> quite often other threads run before the printing is finished

That means the pretty printer is calling functions in the inferior, which then
ends up being the same problem.

The workaround is to switch to one of the threads that GDB knows is stopped
(e.g., thread 22 in your case) and continue that one, or do "stepi" -- when
that step finishes, the threads' states sync up.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-05-05 17:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15  7:56 [Bug threads/18127] New: " palves at redhat dot com
2015-05-05 15:31 ` [Bug threads/18127] " richard_sharman at mitel dot com
2015-05-05 17:07 ` palves at redhat dot com [this message]
2015-05-05 18:05 ` richard.sharman at mitel dot com
2015-06-10 15:33 ` eliz at gnu dot org
2015-06-29 15:55 ` cvs-commit at gcc dot gnu.org
2015-06-29 18:58 ` palves at redhat dot com

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=bug-18127-4717-iLJ7V5dGxK@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).