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: "smark at datto dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 22 Jan 2016 16:02:26 +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
--- Comment #9 from smark at datto dot com ---
So I checked out that fork-bugs branch and rebuilt and ran, and I still get
those "cannot access memory at address..." errors.
Although now there are line breaks whereas the were on the same ine before. So
that's something.
infrun: target_wait (-1.0.0, status) =
infrun: 16975.16975.0 [process 16975],
infrun: status->kind = execd
process 16975 is executing new program: /bin/dash
infrun: TARGET_WAITKIND_EXECD
infrun: Switching context from Thread 0x7ffff7fc77c0 (LWP 16925) to process
16975
Error in re-setting breakpoint 1: Warning:
Cannot insert breakpoint 6.
Cannot access memory at address 0x436825
Cannot insert breakpoint 2.
Cannot access memory at address 0x436845
Error in re-setting breakpoint 2: Warning:
Cannot insert breakpoint 6.
Cannot access memory at address 0x436825
Error in re-setting breakpoint 3: Warning:
Cannot insert breakpoint 6.
Cannot access memory at address 0x436825
Error in re-setting breakpoint 4: Warning:
Cannot insert breakpoint 6.
Cannot access memory at address 0x436825
Error in re-setting breakpoint 5: Warning:
Cannot insert breakpoint 6.
Cannot access memory at address 0x436825
--
You are receiving this mail because:
You are on the CC list for the bug.