Re: [RFA] let record_resume fail immediately on error

[Hui Zhu <teawater@gmail.com>]

The important part is:
(gdb) c
Continuing.

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb) record stop
Process record is not started.

The inferior is dead.

"it looks like GDB
> is stuck on the unsupported instruction, and I'm not sure that this
> is an improvement."

Stop is better than dead, right?

Hui


On Wed, Oct 14, 2009 at 10:42, Joel Brobecker <brobecker@adacore.com> wrote:
>> (gdb) record
>> (gdb) c
>> Continuing.
>> Process record doesn't support instruction rdtsc.
>> Process record doesn't support instruction 0xf31 at address 0x8048352.
>> Process record: failed to record execution log.
>>
>> Program received signal SIGABRT, Aborted.
>
> OK - I can see that there is a SIGABRT, and so I suspect that this
> SIGABRT is a consequence of the problem you're trying to fix.  Can you
> explain the sequence of events that occur inside GDB that cause this
> SIGABRT?  Can you also explain how you are fixing this problem? Again,
> from a copy of the GDB session *after* your patch, it looks like GDB
> is stuck on the unsupported instruction, and I'm not sure that this
> is an improvement.  So I'm assuming that I am not understanding what
> your fix is doing.
>
> --
> Joel
>