|
From: Dirk M. <dm...@gm...> - 2006-09-08 18:18:07
|
On Wednesday 06 September 2006 19:51, Tom Hughes wrote:
> I'm not sure this is anything to worry about - it has crashed
> trying to run the glibc cleanup code but if glibc has already
> corrupted it's state then it's not entirely surprising if that
> fails.
I don't think so - I see it too everywhere even for clean applications. and=
=20
looking at the code its not a surprise:=20
VALGRIND_DO_CLIENT_REQUEST(res, 0 /* default */,
VG_USERREQ__LIBC_FREERES_DONE,=B7
0, 0, 0, 0, 0);
/*NOTREACHED*/
*(int *)0 =3D 'x';
}
The NOTREACHED part is executed for me. Julian said that it might be becaus=
e=20
the compiler optimizes the DO_CLIENT_REQUEST away, but I haven't checked=20
that.=20
Dirk
|