Julian Seward wrote: >> I'm getting a "fatal error: unsupported CPU" on my Via C7 Esther >> processor-based machine running a brand new installation of Slackware >> 13.0. valgrind-3.1.0 ran just fine on the machine before the upgrade. >> > > Really? The minimum requirements haven't changed. I have a very > ancient VIA cpu here which it runs fine on: > > $ cat /proc/cpuinfo > processor : 0 > vendor_id : CentaurHauls > cpu family : 6 > model : 7 > model name : VIA Samuel 2 > stepping : 3 > cpu MHz : 533.349 > cache size : 64 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 de tsc msr cx8 mtrr pge mmx 3dnow up > bogomips : 1066.69 > clflush size : 32 > power management: > > >> installing but can't get ./coregrind/valgrind to tell me anything - it >> can't find memcheck.) >> > > Sounds like your build is broken. Anyway, you shouldn't be running > random bits of the build. Either run vg-in-place or do make install > and run $prefix/bin/valgrind. > > On the above machine, a run "valgrind -d date" produces lots of > debug output, including > > --15887:1:main Get hardware capabilities ... > --15887:1:main ... arch = X86, hwcaps = x86-sse0 > > What happens on your machine? > > J > >
Last time I built valgrind, it worked just fine "out of the box", so I didn't need to learn how to debug it (and I see now that "vg-in-place" didn't exist). Thanks for the information. That's very useful. Under Slackware 11.0, using the machine that still runs valgrind 3.1.0, I get the following with valgrind 3.5.0: # ./vg-in-place -d date --2299:1:debuglog DebugLog system started by Stage 1, level 1 logging requested --2299:1:launcher no tool requested, defaulting to 'memcheck' --2299:1:launcher selected platform 'x86-linux' --2299:1:launcher launching /usr/local/src/valgrind/valgrind-3.5.0/./.in_place/memcheck-x86-linux --2299:1:debuglog DebugLog system started by Stage 2 (main), level 1 logging requested --2299:1:main Welcome to Valgrind version 3.5.0 debug logging --2299:1:main Checking current stack is plausible --2299:1:main Checking initial stack was noted --2299:1:main Starting the address space manager --2299:1:main Address space manager is running --2299:1:main Starting the dynamic memory manager --2299:1:mallocfr newSuperblock at 0x61DC0000 (pszB 4194288) owner VALGRIND/tool --2299:1:main Dynamic memory manager is running --2299:1:main Initialise m_debuginfo --2299:1:main VG_(libdir) = /usr/local/src/valgrind/valgrind-3.5.0/./.in_place --2299:1:main Getting launcher's name ... --2299:1:main ... /usr/local/src/valgrind/valgrind-3.5.0/coregrind/valgrind --2299:1:main Get hardware capabilities ... 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) /proc/cpuinfo on this machine yields: # cat /proc/cpuinfo processor : 0 vendor_id : CentaurHauls cpu family : 6 model : 10 model name : VIA Esther processor 1200MHz stepping : 9 cpu MHz : 1201.143 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 bogomips : 2408.44 The /proc/cpuinfo output on the Slackware 13.0 machine differs slightly, in particular the flags: 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 Finally, a snippet from a 3.1.0 "valgrind -d date" run on the Slackware 11.0 machine: --2301:1:main Get hardware capabilities ... --2301:1:main ... arch = X86, subarch = x86-sse2 Oddly, this does *not* appear when I installed valgrind 3.1.0 on the Slackware 13.0 machine (even after "make uninstall" in the 3.5.0 installation). Instead I get some hundreds of: --5811-- DWARF2 CFI reader: unhandled CFI instruction 0:22 But version 3.1.0 "valgrind -d date" does run on the Slackware 13.0 box. So something has clearly changed in the way that hardware capabilities are retrieved in valgrind, such that Slackware builds on Via CPUs don't return the proper information. I can apply patches or insert debug printf() statements if someone can tell me where to look. I'm swamped right now, so I don't have time to learn a whole lot about the source code. :-( ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
