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: Edjunior Barbosa Machado <emachado at linux dot vnet dot ibm dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: 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>
- Date: Fri, 03 Aug 2012 18:45:53 -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> <20120803202234.GA20454@host2.jankratochvil.net>
On 08/03/2012 05:22 PM, Jan Kratochvil wrote:
> Hi Edjunior,
>
> On Fri, 03 Aug 2012 00:49:08 +0200, Edjunior Barbosa Machado wrote:
>> I've faced this internal-error when running this testcase on Fedora17 (which has valgrind-3.7.0) on ppc64:
>
> FYI I got access to Fedora 17 ppc64 and even there the internal error is not
> reproducible for me:
> kernel-3.3.4-5.fc17.ppc64
> valgrind-3.7.0-4.fc17.ppc64
>
> (It works except for the _start vs. ._start problem.)
>
>
> Thanks,
> Jan
>
As discussed with Jan in the irc channel, the culprit here was the XML support missing. After install expat-devel, valgrind-infcall.exp passed with no failure.
Btw, is there some way to check whether XML support is enabled in order to avoid this on the testcases?
Thanks,
--
Edjunior