Your message dated Sun, 9 Dec 2012 12:43:46 +0100 with message-id <20121209114346.GA5029@wakko> and subject line Re: Bug#688820: valgrind: "fatal error: unsupported CPU." on a Via C7 has caused the Debian Bug report #688820, regarding valgrind: "fatal error: unsupported CPU." on a Via C7 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 688820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688820 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: valgrind Version: 1:3.7.0-6 Severity: important valgrind won't run on this Via C7 CPU: /proc/cpuinfo: processor : 0 vendor_id : CentaurHauls cpu family : 6 model : 10 model name : VIA Esther processor 1200MHz stepping : 9 cpu MHz : 1200.000 cache size : 128 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 apic sep mtrr pge cmov pat clflush acpi mmx fxsr sse sse2 tm nx up pni est tm2 rng rng_en ace ace_en ace2 ace2_en phe phe_en pmm pmm_en bogomips : 2400.41 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 32 bits virtual power management: output of valgrind -d date (seems like my terminal is messed up, probably a utf8 issue): ó¿¶8òõ 8±#8 #8h¼ 8Ô"8h¼ 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:main Welcome to Valgrind version 3.7.0 debug logging X@v¶8ìaó¿¶8òõ 8C@v¶8ìaó¿¶8ð"8J¿ 8Ë 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:main Checking current stack is plausible ug logging X@v¶8ìaó¿¶8òõ 87@v¶8ìaó¿¶8 #8J¿ 8¸Ë 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:main Checking initial stack was noted e ug logging X@v¶8ìaó¿¶8òõ 84@v¶8ìaó¿¶8ä#8J¿ 88Ì 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:main Starting the address space manager ug logging X@v¶8ìaó¿¶8òõ 86@v¶8ìaó¿¶8M$8J¿ 8Ì 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:main Address space manager is running oó¾°ùaÿ¿ùa4@v¶8ìaó¿¶8{$8J¿ 8°Ì 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:main Starting the dynamic memory manager °ùaÿ¿ùa7@v¶8ìaó¿¶8$8J¿ 8ÔÌ 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:mallocfr newSuperblock at 0x61F9C000 (pszB 4194288) owner VALGRIND/tool u¶8u¶8@Su¶8@Àùa £8²!8!8Àùaðÿ?»@$8!8½ 8dynamic memory managP0Èn.8pÿ¿ùaÀùaÀùaî 8@v¶8ìaó¿¶8»8¼ 890«$8¼ 890ÔÌ 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:mallocfr deferred_reclaimSuperblock at 0x61F9C000 (pszB 4194288) (prev 0x0) own8ÿ¿9bÀùaZÈn.8Àùa»@$8¶8<8²!8H !8Àùaðÿ?»@$8!8½ 8Àùa`ðùaðÿ? Ï?@v¶8ìaó¿¶87»8Àùa·$8Àùa90ÔÌ 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿er VALGRIND/tool deferred_reclaimSuperblock at 0x61F9C000 (pszB 4194288) (prev 0x0) own8ÿ¿9bÀùaÈn.8Àùa»@$8¶8<8²!8H !8Àùaðÿ?»@$8!8½ 8Àùa`ðùaðÿ? Ï?@v¶8ìaó¿¶87»8Àùa·$8Àùa90ÔÌ 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:main Dynamic memory manager is running ?»@$8!8½ 8Àùa`ðùaðÿ? Ï?@v¶8ìaó¿5@v¶8ìaó¿¶8Ó$8J¿ 8üÌ 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:main Initialise m_debuginfo s running ?»@$8!8½ 8Àùa`ðùaðÿ? Ï?@v¶8ìaó¿*@v¶8ìaó¿¶8ï$8J¿ 8¼ 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:main VG_(libdir) = /usr/lib/valgrind ?»@$8!8ó¿XPý8¶¼ 8ó¿ ìaó¿3@v¶8ìaó¿¶8.%8J¿ 8ü 8ȷ 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:main Getting launcher's name ... nd ?»@$8!8ó¿XPý8¶¼ 8ó¿ ìaó¿/@v¶8ìaó¿¶8J%8J¿ 8ռ 8ȷ 8ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:main ... /usr/bin/valgrind.bin nd ?»@$8!8ó¿XPý8C· 8ó¿ìaó¿-@v¶8ìaó¿¶8%8J¿ 8ò¼ 8ó¿ôaó¿äaó¿àaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿--25299:1:main Get hardware capabilities ... u¶88u¶8¿èFå81@v¶8ìaó¿¶8â%8J¿ 8|Í 8ó¿ôaó¿äaó¿ÿÿÿÿàaó¿°¶8ôaó¿ôaó8¬k.8,!8àaó¿ÿÿÿÿÿÿÿÿÿÿÿÿ valgrind: fatal error: unsupported CPU. Supported CPUs are: * x86 (practically any; Pentium-I or above), AMD Athlon or above) * AMD Athlon64/Opteron * PowerPC (most; ppc405 and above) * System z (64bit only - s390x; z900 and above) output of valgrind -d date: -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages valgrind depends on: ii libc6 2.13-35 ii libc6-dbg 2.13-35 Versions of packages valgrind recommends: ii gdb 7.4.1-1.1 pn valgrind-dbg <none> Versions of packages valgrind suggests: pn alleyoop <none> pn kcachegrind <none> pn valgrind-mpi <none> pn valkyrie <none> -- no debconf information
--- End Message ---
--- Begin Message ---On mer, set 26, 2012 at 06:43:15 +0200, Alessandro Ghedini wrote: > Hi, > > On Wed, Sep 26, 2012 at 12:09:44AM +0200, david wrote: > > flags : fpu vme de pse tsc msr pae mce apic sep mtrr pge cmov > > pat clflush acpi mmx fxsr sse sse2 tm nx up pni est tm2 rng rng_en ace > > ace_en ace2 ace2_en phe phe_en pmm pmm_en > > Looks like the "cx8" flag is not present which should mean that the CMPXCHG8 > instruction is not supported, which in turn is a requirement to run valgrind > on > x86 (well, according to the comments in the code anyway). > > So, I don't think much can be done about this (also note that I can't test > this > since I don't have such CPU). Closing this. Cheers -- perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
signature.asc
Description: Digital signature
--- End Message ---
