Re: [commit+7.5] [patchv2] Write bpt at the ON_STACK bpt address

Sergio Durigan Junior
2012-08-03T01:48:12Z

On Thursday, August 02 2012, Pedro Alves wrote:

>>> Program received signal SIGTRAP, Trace/breakpoint trap.
>>> ../../gdb.git/gdb/frame.c:2396: internal-error: frame_cleanup_after_sniffer: Assertion `frame->prologue_cache == NULL' failed.
>>> A problem internal to GDB has been detected,
>>> FAIL: gdb.base/valgrind-infcall.exp: continue (GDB internal error)
>>> further debugging may prove unreliable.
>>> Quit this debugging session? (y or n) n
>>>
>>> With this error, gdb connection is closed and the testsuite gets stuck
>>> at this point.
>>
>> (Adding Tom to CC list).
>>
>> Thanks for the report.
>>
>> Just as an FYI (or For Our Information, rather),
>> http://sourceware.org/ml/gdb-patches/2012-08/msg00075.html clearly fixes
>> the bug. I will keep an eye on this since I am interested as well.
>
> Curious. But is the cause the same? If something sending C-c to gdb at the "wrong" time?

Not sure, but apparently not. I just wanted to make the relation
between the patch and the problem clear. It is also worth noting that
the patch fixes only the internal error, but some failures still occur,
which is something else to be investigated.

--
Sergio