This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [commit+7.5] [patchv2] Write bpt at the ON_STACK bpt address
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Edjunior Barbosa Machado <emachado at linux dot vnet dot ibm dot com>
- Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>, Philippe Waroquiers <philippe dot waroquiers at skynet dot be>, Pedro Alves <palves at redhat dot com>, Joel Brobecker <brobecker at adacore dot com>, gdb-patches at sourceware dot org, "Maciej W. Rozycki" <macro at codesourcery dot com>, Tom Tromey <tromey at redhat dot com>
- Date: Thu, 02 Aug 2012 20:09:00 -0300
- Subject: Re: [commit+7.5] [patchv2] Write bpt at the ON_STACK bpt address
- References: <5012B1B6.1030003@redhat.com> <1343339398.2258.119.camel@soleil> <20120727184633.GA14182@host2.jankratochvil.net> <20120731073643.GA18696@host2.jankratochvil.net> <501B03E4.1020209@linux.vnet.ibm.com>
On Thursday, August 02 2012, Edjunior Barbosa Machado wrote:
> On 07/31/2012 04:36 AM, Jan Kratochvil wrote:
>>> gdb/testsuite/
>>> 2012-07-27 Jan Kratochvil <jan.kratochvil@redhat.com>
>>>
>>> * gdb.base/valgrind-infcall.c: New file.
>>> * gdb.base/valgrind-infcall.exp: New file.
>
> I've faced this internal-error when running this testcase on Fedora17 (which has valgrind-3.7.0) on ppc64:
>
> ...
> (gdb) PASS: gdb.base/valgrind-infcall.exp: continue #1 (false warning)
> continue
> Continuing.
> ==7541== Invalid free() / delete / delete[] / realloc()
> ==7541== at 0x40458BC: free (vg_replace_malloc.c:427)
> ==7541== by 0x10000763: main (valgrind-infcall.c:38)
> ==7541== Address 0x4070040 is 0 bytes inside a block of size 1 free'd
> ==7541== at 0x40458BC: free (vg_replace_malloc.c:427)
> ==7541== by 0x10000757: main (valgrind-infcall.c:37)
> ==7541==
> ==7541== (action on error) vgdb me ...
>
> 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.
Thanks,
--
Sergio