Re: [Valgrind-developers] ACATS c45624a and c45624b

[Julian S. <js...@ac...>]

On Monday 18 July 2005 14:20, Nicholas Nethercote wrote:
> On Mon, 18 Jul 2005, Duncan Sands wrote:
> > These both fail in similar ways:
> >
> > ,.,. C45624A ACATS 2.5 05-07-18 00:19:06
> > ---- C45624A FOR FLOATING POINT TYPES, CHECK THAT CONSTRAINT_ERROR IS
> >                RAISED IF MACHINE_OVERFLOWS IS FALSE.  THIS TESTS DIGITS
> >                5.
> >   - C45624A CONSTRAINT_ERROR WAS NOT RAISED WHEN MACHINE_OVERFLOWS WAS
> >                FALSE.
> > 0:I1
> > vex: the `impossible' happened:
> >   iselCondCode
> > vex storage:  P 512,  T total 85688840 (2710216),  T curr 136584 (4423)
> >
> > valgrind: the 'impossible' happened:
> >   LibVEX called failure_exit().

Ok, that was straightforward.  Either of vex r1275 or r1276 fixes it.
Pls try.  You'll also need to update your valgrind tree due to massive
ppc hacking over the weekend.

Next: can you send me a binary of one of the tests that appears not to
terminate running on V ?  Also the ada source would be good, so I can
get some idea of what it's trying to do.

J