[Bug c++/23354] New: gdb core dump when debugging program that forks.

[smark at datto dot com]

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

Bug ID: 23354
Summary: gdb core dump when debugging program that forks.
Product: gdb
Version: 7.12.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
Assignee: unassigned at sourceware dot org
Reporter: smark at datto dot com
Target Milestone: ---

gdb told me to file a bug so I am....

linux-nat.c:1752: internal-error: void linux_nat_resume(target_ops*, ptid_t,
int, gdb_signal): Assertion `lp != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n

This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.

linux-nat.c:1752: internal-error: void linux_nat_resume(target_ops*, ptid_t,
int, gdb_signal): Assertion `lp != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
infcall.c:1160: internal-error: value* call_function_by_hand_dummy(value*, int,
value**, void (*)(void*, int), void*): Assertion `tp->thread_fsm ==
&sm->thread_fsm' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) ^C

[smark at datto dot com]

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

--- Comment #1 from smark at datto dot com ---
I have a core dump if you want, but it's too big to attach

[smark at datto dot com]

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

--- Comment #2 from smark at datto dot com ---
also happens in gdb 8.1

linux-nat.c:1767: internal-error: void linux_nat_resume(target_ops*, ptid_t,
int, gdb_signal): Assertion `lp != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

[smark at datto dot com]

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

smark at datto dot com changed:

What |Removed |Added
----------------------------------------------------------------------------
Version|7.12.1 |8.1

[smark at datto dot com]

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

smark at datto dot com changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |smark at datto dot com

[smark at datto dot com]

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

--- Comment #3 from smark at datto dot com ---
So I have a program that forks a child process and via pipe tells that process
to run commands which will then call fork.

I do this via eclipse cdt and I find when I "run" over the fork (I have gdb
following the parent not the child) it usually works, but when I step over it,
it most of the time runs into this problem, if that's any help.

Again, tell me where to put a core dump and I can do that.

[palves at redhat dot com]

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

Pedro Alves <palves at redhat dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com

--- Comment #4 from Pedro Alves <palves at redhat dot com> ---
Hi. Thanks for reporting the bug.

A gdb core dump isn't very useful for this kind of bug.

A small self-contained reproducer we can run on the command line is much more
more useful.

[smark at datto dot com]

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

--- Comment #5 from smark at datto dot com ---
It'll take me a bit as I'm currently supporting a newly implemented production
system but I will definitely get to this because it's really hurting me,
thanks.