This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/19503] internal-error: linux_nat_resume: Assertion `lp != NULL' failed.
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 21 Jan 2016 22:58:08 +0000
- Subject: [Bug gdb/19503] internal-error: linux_nat_resume: Assertion `lp != NULL' failed.
- Auto-submitted: auto-generated
- References: <bug-19503-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19503
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
Hi.
This is:
static void
linux_nat_resume (struct target_ops *ops,
ptid_t ptid, int step, enum gdb_signal signo)
{
...
if (resume_many)
lp = find_lwp_pid (inferior_ptid);
else
lp = find_lwp_pid (ptid);
gdb_assert (lp != NULL);
GDB core told the ptrace layer to resume a thread that the ptrace layer thinks
doesn't exist. This assertion is still present in master. I've never seen it
trigger before. There's no workaround.
It's unfortunately impossible to debug this sort of problem from the
internal-error alone. We'd need to see "set debug infrun 1 + set debug lin-lwp
1" logs, and/or have a small reproducer we could try ourselves.
--
You are receiving this mail because:
You are on the CC list for the bug.