|
From: Melchior F. <mel...@gm...> - 2008-02-24 14:16:08
Attachments:
vg.log.gz
|
With valgrind from SVN from a few minutes ago (r7436), I get this
(full log attached):
$ valgrind --tool=memcheck osgkeyboard 2>&1|tee /tmp/vg.log
[...]
IR SANITY CHECK FAILURE
[...]
IN STATEMENT:
t73 = SetV128lo32(t72,t68)
ERROR = Iex.Binop: arg tys don't match op tys
... additional details precede BB printout
vex: the `impossible' happened:
sanityCheckFail: exiting due to bad IR
vex storage: T total 1064441312 bytes allocated
vex storage: P total 672 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
==22646== at 0x3801818D: report_and_quit (m_libcassert.c:140)
==22646== by 0x3801829B: panic (m_libcassert.c:210)
==22646== by 0x38018332: vgPlain_core_panic_at (m_libcassert.c:215)
==22646== by 0x38018370: vgPlain_core_panic (m_libcassert.c:220)
==22646== by 0x3802D5A6: failure_exit (m_translate.c:588)
==22646== by 0x380898AE: vpanic (vex_util.c:227)
==22646== by 0x38084C7C: sanityCheckFail (irdefs.c:2077)
==22646== by 0x380858B4: tcExpr (irdefs.c:2364)
==22646== by 0x38086052: sanityCheckIRSB (irdefs.c:2460)
==22646== by 0x38088164: LibVEX_Translate (vex_main.c:521)
==22646== by 0x3802BEBE: vgPlain_translate (m_translate.c:1417)
==22646== by 0x38035BAF: vgPlain_scheduler (scheduler.c:770)
==22646== by 0x38049258: run_a_thread_NORETURN (syswrap-linux.c:89)
m.
|
|
From: Julian S. <js...@ac...> - 2008-02-24 14:29:47
|
Try 'make distclean' and a rebuild. J On Sunday 24 February 2008 15:16, Melchior FRANZ wrote: > With valgrind from SVN from a few minutes ago (r7436), I get this > (full log attached): > > > $ valgrind --tool=memcheck osgkeyboard 2>&1|tee /tmp/vg.log > [...] > IR SANITY CHECK FAILURE > [...] > IN STATEMENT: > > t73 = SetV128lo32(t72,t68) > > ERROR = Iex.Binop: arg tys don't match op tys > ... additional details precede BB printout > > > > vex: the `impossible' happened: > sanityCheckFail: exiting due to bad IR > vex storage: T total 1064441312 bytes allocated > vex storage: P total 672 bytes allocated > > valgrind: the 'impossible' happened: > LibVEX called failure_exit(). > ==22646== at 0x3801818D: report_and_quit (m_libcassert.c:140) > ==22646== by 0x3801829B: panic (m_libcassert.c:210) > ==22646== by 0x38018332: vgPlain_core_panic_at (m_libcassert.c:215) > ==22646== by 0x38018370: vgPlain_core_panic (m_libcassert.c:220) > ==22646== by 0x3802D5A6: failure_exit (m_translate.c:588) > ==22646== by 0x380898AE: vpanic (vex_util.c:227) > ==22646== by 0x38084C7C: sanityCheckFail (irdefs.c:2077) > ==22646== by 0x380858B4: tcExpr (irdefs.c:2364) > ==22646== by 0x38086052: sanityCheckIRSB (irdefs.c:2460) > ==22646== by 0x38088164: LibVEX_Translate (vex_main.c:521) > ==22646== by 0x3802BEBE: vgPlain_translate (m_translate.c:1417) > ==22646== by 0x38035BAF: vgPlain_scheduler (scheduler.c:770) > ==22646== by 0x38049258: run_a_thread_NORETURN (syswrap-linux.c:89) > > m. |
|
From: Melchior F. <mel...@gm...> - 2008-02-24 14:47:19
|
* Julian Seward -- Sunday 24 February 2008: > Try 'make distclean' and a rebuild. Argh ... yes, that helped. (I'm just not used to having to do the build system's job. ;-) Thanks, and sorry for the noise! m. |