Bug 373288

Summary:	are_valid_hwcaps VexArchAMD64 assert error
Product:	[Developer tools] valgrind	Reporter:	Rishikesh Satralkar <rsatralkar>
Component:	general	Assignee:	Julian Seward <jseward>
Status:	REPORTED ---
Severity:	normal	CC:	philippe.waroquiers
Priority:	NOR
Version First Reported In:	3.8.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Rishikesh Satralkar 2016-12-05 12:22:24 UTC

-Observed following while doing valgrind,

x: priv/main_main.c:319 (LibVEX_Translate): Assertion `are_valid_hwcaps(VexArchAMD64, vta->archinfo_host.hwcaps)' failed.
vex storage: T total 0 bytes allocated
vex storage: P total 0 bytes allocated

valgrind: the 'impossible' happened:
   LibVEX called failure_exit().
==21964==    at 0x38031DA7: report_and_quit (m_libcassert.c:235)
==21964==    by 0x38031E0E: panic (m_libcassert.c:319)
==21964==    by 0x38031E68: vgPlain_core_panic_at (m_libcassert.c:324)
==21964==    by 0x38031E7A: vgPlain_core_panic (m_libcassert.c:329)
==21964==    by 0x3804D162: failure_exit (m_translate.c:708)
==21964==    by 0x380D4C38: vex_assert_fail (main_util.c:219)
==21964==    by 0x380D3009: LibVEX_Translate (main_main.c:319)
==21964==    by 0x3804AACE: vgPlain_translate (m_translate.c:1559)
==21964==    by 0x38079D9F: vgPlain_scheduler (scheduler.c:991)
==21964==    by 0x380A6409: run_a_thread_NORETURN (syswrap-linux.c:103)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable
==21964==    at 0x4000B00: ??? (in /lib64/ld-2.12.so)


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

Comment 1 Philippe Waroquiers 2016-12-06 18:59:03 UTC

Is this really related to Valgrind version 3.8.0 ?
This is obsolete/not maintained anymore.

Please upgrade to the last release (3.12.0) and retry.

Assuming you are using or have upgraded to 3.12.0 and problem still there,
please provide more information:
* which Linux distribution ?
* cat /proc/cpuinfo
* attach the output of    valgrind -v -v -v -d -d -d date

Thanks