|
From: Yeshurun, M. <mei...@in...> - 2005-07-29 10:35:13
|
The problem has been solved. Thanks.
=20
________________________________
From: val...@li...
[mailto:val...@li...] On Behalf Of
Yeshurun, Meir
Sent: Friday, July 29, 2005 9:58 AM
To: val...@li...
Subject: [Valgrind-users] PIE Valgrind
=20
=20
=20
Hi,
=20
I built Valgrind as a PIE by specifying --enable-pie when running the
configure script, but now Valgrind fails even on "hello world" programs
(see (part of) the output below).
=20
Why is this happening?
=20
Thanks,
=20
Meir
=20
=20
=20
=3D=3D8661=3D=3D Memcheck, a memory error detector.
=3D=3D8661=3D=3D Copyright (C) 2002-2005, and GNU GPL'd, by Julian =
Seward et al.
=3D=3D8661=3D=3D Using LibVEX rev 1271M, a library for dynamic binary
translation.
=3D=3D8661=3D=3D Copyright (C) 2004-2005, and GNU GPL'd, by OpenWorks =
LLP.
=3D=3D8661=3D=3D Using valgrind-3.0.0.SVN, a dynamic binary =
instrumentation
framework.
=3D=3D8661=3D=3D Copyright (C) 2000-2005, and GNU GPL'd, by Julian =
Seward et al.
=3D=3D8661=3D=3D For more details, rerun with: -v
=3D=3D8661=3D=3D=20
=20
IR SANITY CHECK FAILURE
=20
IRBB {
t0:I64 t1:I64 t2:I64 t3:I64 t4:I64 t5:I64 t6:I64 t7:I64
t8:I64 t9:I64 t10:I64 t11:I64 t12:I64 t13:I64 t14:I64
t15:I64
t16:I64 t17:I64 t18:I64 t19:I64 t20:I64 t21:I8 t22:I64
t23:I64
t24:I64 t25:I64 t26:I64 t27:I64 t28:I64 t29:I64 t30:I64
t31:I64
t32:I64 t33:I64 t34:I64 t35:I64 t36:I64 t37:I64 t38:I64
t39:I64
t40:I64 t41:I64 t42:I64 t43:I64 t44:I64 t45:I64 t46:I64
t47:I64
t48:I64 t49:I64 t50:I64 t51:I64 t52:I64 t53:I64 t54:I64
t55:I64
t56:I64 t57:I64 t58:I64 t59:I64 t60:I64 t61:I64 t62:I8
t63:I8
t64:I64 t65:I64 t66:I64 t67:I64 t68:I64 t69:I64 t70:I64
t71:I32
t72:I64 t73:I64 t74:I64 t75:I64 t76:I64 t77:I64 t78:I64
t79:I1
t80:I64 t81:I64 t82:I64 t83:I64 t84:I64 t85:I64 t86:I64
t87:I64
t88:I64 t89:I64 t90:I1 t91:I64 t92:I64 t93:I64 t94:I64
t95:I64
=20
...........
=20
=20
helperc_value_check8_fail){
0x7FB1562060}()
goto {Boring} 0x1402601181:I64
}
=20
IN STATEMENT:
=20
t143 =3D 32Uto64(t142)
=20
ERROR =3D IRStmt.Put.Tmp: tmp and expr do not match
=20
=20
vex: the `impossible' happened:
sanityCheckFail: exiting due to bad IR
vex storage: P 0, T total 0 (0), T curr 80272 (1546)
=20
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
=3D=3D8661=3D=3D at 0x7FB0021A43: vgPlain_core_panic_at =
(m_libcassert.c:181)
=3D=3D8661=3D=3D by 0x7FB014FFFF: ???
=3D=3D8661=3D=3D by 0x7FB00C77BB: dis_op2_E_G (toIR.c:2412)
=3D=3D8661=3D=3D by 0x7FB014F8DF: ???
=20
sched status:
running_tid=3D1
=20
Thread 1: status =3D VgTs_Runnable
=3D=3D8661=3D=3D at 0x1402600CF0: (within /lib64/ld-2.3.3.so)
=20
=20
Note: see also the FAQ.txt in the source distribution.
It contains workarounds to several common problems.
=20
If that doesn't help, please report this bug to: www.valgrind.org
=20
In the bug report, send all the above text, the valgrind
version, and what Linux distro you are using. Thanks.
|