Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#21536 - [valgrind] handle_intel: Assertion 'maxid >= 2' failed

Attached to Project: Arch Linux
Opened by João Vieira (Vieira) - Saturday, 30 October 2010, 19:14 GMT
Last edited by Allan McRae (Allan) - Friday, 03 December 2010, 11:40 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Allan McRae (Allan)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Running valgrind with any program (e.g. valgrind ls) always stops with this error:
.../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx >= 2'

I can only reproduce this error on one of my machines which uses a AMD Athlon Processor.

> cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 4
model name : AMD Athlon(tm) Processor
stepping : 4
cpu MHz : 896.731
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat
pse36 mmx fxsr syscall mmxext 3dnowext 3dnow up
bogomips : 1794.18
clflush size : 32
cache_alignment : 32
address sizes : 36 bits physical, 32 bits virtual
power management:

Additional info:
* valgrind-3.6.0-1; glibc-2.12.1-3
*debian-glibc@lists.debian.org/msg43820.html"> http://www.mail-archive.com/debian-glibc@lists.debian.org/msg43820.html

Steps to reproduce:
1) In a machine with the specified cpu run valgrind with any application as argument.
2) Execution is prematurely aborted with assertion handle_intel: Assertion `maxidx >= 2'
This task depends upon

Closed by  Allan McRae (Allan)
Friday, 03 December 2010, 11:40 GMT
Reason for closing:  Deferred
Additional comments about closing:  Will fix when someone with relevant CPU provides more details.
Comment by Allan McRae (Allan) - Sunday, 31 October 2010, 08:44 GMT Comment by Allan McRae (Allan) - Thursday, 11 November 2010, 02:12 GMT
According to the Debian bug report, it is fixed with a newer SVN snapshot. However, it looks like the revision they are using is older than the 3.6 release...

Can someone affected by this try building from SVN and if that works figure out which revision fixes it? I do not have the processor to test this out myself.

Loading...