Re: [PATCH] Quit after debugging corefiles

[Michael Snyder <msnyder@vmware.com>]

Edjunior Barbosa Machado wrote:
> Hello,
> 
> when quitting after a successful debug using a corefile, gdb returns the following internal error:
> 
> ...
> (gdb) cont
> Continuing.
> 
> Program exited normally.
> (gdb) quit

Hmm, I don't think you're supposed to "continue" when debugging a core 
file...

> ../../git/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) n
> ../../git/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) n
> 
> Please consider the following patch containing a fix and a new test for the gcore.exp testcase. It also proposes a change in the function called by gdb_test_multiple that deals with internal error (proc gdb_internal_error_resync{}, in gdb.exp) in order to recognize that gdb is finished.
> 
> Comments/suggestions are welcome.
> 
> Thanks,