public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17408] ../../gdb/infrun.c:5256: internal-error: switch_back_to_stepped_thread: Assertion `!schedlock_applies (1)' failed.
Date: Thu, 18 Sep 2014 00:25:00 -0000 [thread overview]
Message-ID: <bug-17408-4717-OBgP7xiZXW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17408-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17408
--- Comment #3 from dje at google dot com ---
(In reply to dje from comment #2)
> I don't see the SIGTRAP for thread 25666 having come in before a "next" was
> done.
Ah. We're stepping over a function call here, in which case all threads are
run.
Presumably the assert isn't handling this case.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-09-18 0:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 22:45 [Bug gdb/17408] New: " jstpierre at mecheye dot net
2014-09-17 23:11 ` [Bug gdb/17408] " sergiodj at redhat dot com
2014-09-18 0:03 ` dje at google dot com
2014-09-18 0:25 ` dje at google dot com [this message]
2014-10-24 12:07 ` palves at redhat dot com
2014-10-29 18:25 ` cvs-commit at gcc dot gnu.org
2014-10-29 18:27 ` cvs-commit at gcc dot gnu.org
2014-10-29 18:33 ` cvs-commit at gcc dot gnu.org
2014-10-29 18:35 ` palves at redhat dot com
2014-10-29 19:48 ` cvs-commit at gcc dot gnu.org
2014-12-25 0:46 ` cvs-commit at gcc dot gnu.org
2021-10-21 6:52 ` bap.fayol at gmail 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-17408-4717-OBgP7xiZXW@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).