|
From: Xavier Barnabe-T.
|
Hello I tried to get valgrind-20030716 working with=20 calltree-0.9.1 and of course=20 kcachegrind-0.3b on Mandrake Linux release 9.1 (Bamboo) for i586. Everything compiles. But to get trough the configure of calltree, I modified the line about the cvs version of valgrind, not accepting valgrind-cvs-head-2003... but valgrind-20030716. Then it works. valgrind with default skin works great, telling me that no error was found on my testing program. valgrind with calltree skin gets the following error message at some stage: valgrind: vg_translate.c:658 (vgPlain_saneUCodeBlock): Assertion `sane' failed. and emits an empty output cachegrind.out.XXXX file. The complete output of the run with calltree appears at the end. valgrind with cachegrind seems to work, giving some output in the cachegrind.out.XXXX. kcachegrind seems to work as well. Except that I get no information about my program (a small testing program). If some have ideas, thank you. Don't hesitate to ask for more information. Xavier ---------------------------------------------------------------- =3D=3D6758=3D=3D Calltree-0.9.1, a cache profiler for x86-linux. =3D=3D6758=3D=3D Copyright (C) 2002, and GNU GPL'd, by N.Nethercote and J.W= eidendorfer. =3D=3D6758=3D=3D Using valgrind-20030716, a program supervision framework f= or x86-linux. =3D=3D6758=3D=3D Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. =3D=3D6758=3D=3D Estimated CPU clock rate is 401 MHz =3D=3D6758=3D=3D For more details, rerun with: -v =3D=3D6758=3D=3D=20 Instruction failed sanity check: =09 1: CALLMo =09t4=09=09[abcdSD] opcode: 68 lit32: 0x4002021A size: 0 val1,val2,val3: 4, 0, 0 tag1,tag2,tag3: 0, 7, 7 flags_r: 0x0 flags_w: 0x0 extra4b: 0x0 cond: 0x0 signed_widen: 0 jmpkind: 0 argc,regparms_n: 1, 1 has_ret_val: 0 regs_live_after: [abcdSD] valgrind: vg_translate.c:658 (vgPlain_saneUCodeBlock): Assertion `sane' fai= led. sched status: Thread 1: status =3D Runnable, associated_mx =3D 0x0, associated_cv =3D 0x0 =3D=3D6758=3D=3D at 0x4007CF78: (within /net/theorie/auto/home3/xavier/l= ib/valgrind/valgrind.so) =3D=3D6758=3D=3D by 0x4000ABB2: _dl_init_internal (dl-init.c:68) =3D=3D6758=3D=3D by 0x40000AAC: (within /lib/ld-2.3.1.so) Note: see also the FAQ.txt in the source distribution. It contains workarounds to several common problems. If that doesn't help, please report this bug to: js...@ac... In the bug report, send all the above text, the valgrind version, and what Linux distro you are using. Thanks. --=20 Xavier Barnabe-Theriault, PhD student. http://xebu.org/ Institut f=FCr Theoretische Physik Georg-August-Universit=E4t Tammanstrasse 1 37077 G=F6ttingen |
|
From: Josef W. <Jos...@in...> - 2003-07-17 12:05:01
|
On Thursday 17 July 2003 12:24, Xavier Barnabe-Theriault wrote: > Hello > [...] > Everything compiles. But to get trough the configure of calltree, I > modified the line about the cvs version of valgrind, not accepting > valgrind-cvs-head-2003... but valgrind-20030716. Then it works. > > valgrind with default skin works great, telling me that no error was > found on my testing program. > > valgrind with calltree skin gets the following error message at some > stage: > valgrind: vg_translate.c:658 (vgPlain_saneUCodeBlock): Assertion `sane' > failed. Hi, known problem. This error is because of changes between vg_skin.h delivered with calltree and the vg_skin.h from Valgrind CVS. If you change the configure check, you also should copy vg_skin.h from Valgrind CVS to the include-cvs/ directory of the calltree distribution. Some "#include" line of vg_skin.h has to be changed too, to make it compile. It should be clear by the error message you get when compiling. (The error message above suggests a change in the enum for UCodes, e.g. if a UCode was added to support some SSE/MMX Opcode). The big problem is that Valgrind doesn't (yet) install this header file, so external skins have to provide an own version, which not necessarily matches to one your Valgrind was compiled with. This of course only is true for CVS versions, as they are changing regularly. BTW, the above error message never should happen. Instead, valgrind should give out a warning about an old calltree skin. But enforcing this policy only makes sense for realeases, not CVS versions. And thanks for this "bug report", I will include a check in the next calltree release. Josef > and emits an empty output cachegrind.out.XXXX file. The complete output > of the run with calltree appears at the end. > > valgrind with cachegrind seems to work, giving some output in the > cachegrind.out.XXXX. kcachegrind seems to work as well. Except that I > get no information about my program (a small testing program). > > > If some have ideas, thank you. Don't hesitate to ask for more > information. > > > Xavier > > ---------------------------------------------------------------- > > ==6758== Calltree-0.9.1, a cache profiler for x86-linux. > ==6758== Copyright (C) 2002, and GNU GPL'd, by N.Nethercote and > J.Weidendorfer. ==6758== Using valgrind-20030716, a program supervision > framework for x86-linux. ==6758== Copyright (C) 2000-2003, and GNU GPL'd, > by Julian Seward. ==6758== Estimated CPU clock rate is 401 MHz > ==6758== For more details, rerun with: -v > ==6758== > Instruction failed sanity check: > 1: CALLMo t4 [abcdSD] > opcode: 68 > lit32: 0x4002021A > size: 0 > val1,val2,val3: 4, 0, 0 > tag1,tag2,tag3: 0, 7, 7 > flags_r: 0x0 > flags_w: 0x0 > extra4b: 0x0 > cond: 0x0 > signed_widen: 0 > jmpkind: 0 > argc,regparms_n: 1, 1 > has_ret_val: 0 > regs_live_after: [abcdSD] > > valgrind: vg_translate.c:658 (vgPlain_saneUCodeBlock): Assertion `sane' > failed. > > sched status: > > Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 > ==6758== at 0x4007CF78: (within > /net/theorie/auto/home3/xavier/lib/valgrind/valgrind.so) ==6758== by > 0x4000ABB2: _dl_init_internal (dl-init.c:68) > ==6758== by 0x40000AAC: (within /lib/ld-2.3.1.so) > > > Note: see also the FAQ.txt in the source distribution. > It contains workarounds to several common problems. > > If that doesn't help, please report this bug to: js...@ac... > > In the bug report, send all the above text, the valgrind > version, and what Linux distro you are using. Thanks. -- -- Dr. Josef Weidendorfer LRR-TUM - Raum 01.06.056 - Tel. +49 / (0)89 / 289 - 18454 |
|
From: Josef W. <Jos...@gm...> - 2003-07-17 12:12:24
|
On Thursday 17 July 2003 12:24, Xavier Barnabe-Theriault wrote: > Hello > > I tried to get > valgrind-20030716 Ooops... Just noted that valgrind-20030716 *is* a stable release ;-) I will upload a calltree-0.9.2 shortly. Thanks, Josef |
|
From: Xavier Barnabe-T.
|
Hello Many thanks. copying, adjusting only two #includes, make clean, configure, make and make install. It works well. last but not least: enjoy. valgrind + skins + kcachegrind ==> a powerfull and easy tool !! -- Xavier Barnabe-Theriault, PhD student. Institut fuer Theoretische Physik Georg-August-Universitaet Tammanstrasse 1 37077 Goettingen |