This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/17408] ../../gdb/infrun.c:5256: internal-error: switch_back_to_stepped_thread: Assertion `!schedlock_applies (1)' failed.
- From: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 18 Sep 2014 00:03:21 +0000
- Subject: [Bug gdb/17408] ../../gdb/infrun.c:5256: internal-error: switch_back_to_stepped_thread: Assertion `!schedlock_applies (1)' failed.
- Auto-submitted: auto-generated
- References: <bug-17408-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17408
dje at google dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dje at google dot com
--- Comment #2 from dje at google dot com ---
Data point: This is with a Fedora gdb where the default scheduler-locking mode
is "step".
According to the debug log, another thread hit a SIGTRAP while stepping.
But we're in scheduler-locking=step mode ...
I don't see the SIGTRAP for thread 25666 having come in before a "next" was
done.
[According to Jasper, a "next" is done after hitting breakpoint 1.]
--
You are receiving this mail because:
You are on the CC list for the bug.