Under Natty, I experience an odd issue when trying to use a core dump with gdb. In particular, when exiting gdb, I can see the following error message:
Steps to reproduce:
1) Start bash and type "ulimit -c unlimited" to enable core dumps.
2) Compile any C or C++ source file that causes a segfault. (One has already been attached)
3) Run the executable and then type "gdb progname dump", where progname is the name of the program and dump is the core dump.
4) Type "run" in gdb, wait for the program to crash and type "quit", "y".
5) The following is displayed:
/build/buildd/gdb-7.2/gdb/inferior.c:362: internal-error: find_inferior_pid: Assertion `pid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
/build/buildd/gdb-7.2/gdb/inferior.c:362: internal-error: find_inferior_pid: Assertion `pid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
Under Natty, I experience an odd issue when trying to use a core dump with gdb. In particular, when exiting gdb, I can see the following error message:
/build/ buildd/ gdb-7.2/ gdb/inferior. c:362: internal-error: find_inferior_pid: Assertion `pid != 0' failed.
Steps to reproduce:
1) Start bash and type "ulimit -c unlimited" to enable core dumps.
2) Compile any C or C++ source file that causes a segfault. (One has already been attached)
3) Run the executable and then type "gdb progname dump", where progname is the name of the program and dump is the core dump.
4) Type "run" in gdb, wait for the program to crash and type "quit", "y".
5) The following is displayed:
/build/ buildd/ gdb-7.2/ gdb/inferior. c:362: internal-error: find_inferior_pid: Assertion `pid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
/build/ buildd/ gdb-7.2/ gdb/inferior. c:362: internal-error: find_inferior_pid: Assertion `pid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y