This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/19503] internal-error: linux_nat_resume: Assertion `lp != NULL' failed.


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

--- Comment #5 from Pedro Alves <palves at redhat dot com> ---
I do see several forks:

> infrun: target_wait (-1.0.0, status) =
> infrun:   15913.15977.0 [Thread 0x7fffeaffd700 (LWP 15977)],
> infrun:   status->kind = forked
> infrun: TARGET_WAITKIND_FORKED

along with:

> Reading symbols from /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.21.so...done.
> Error in re-setting breakpoint 1: Cannot access memory at address 0x47e956
> Error in re-setting breakpoint 2: Cannot access memory at address 0x47e956
> Error in re-setting breakpoint 3: Cannot access memory at address 0x47e956
> Error in re-setting breakpoint 4: Cannot access memory at address 0x433470

So I wonder whether this series would fix your bug too:

  https://sourceware.org/ml/gdb-patches/2016-01/msg00443.html

That is pushed on the users/palves/fork-bugs branch on the upstream git repo.
Could you give that a try and see if it fixes it for you?

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]