Nabble - Valgrind

Re: Unable to install valkyrie-1.4.0 on Ubuntu

2009-12-07T01:48:45Z

afair, Valkyrie is a Qt 3 application.
It isn't ported to Qt 4.

On Sun, Dec 6, 2009 at 1:54 AM, Suresh Venkata
<suresh.venkata123@...> wrote:
> Qt 4.5.3 sdk installed in /opt/qtsdk-2009.04/qt and valgrind-3.4.1-Debian
> installed on the Ubuntu machine.Is it required to define Qt environment
> variables so that valkyrie identifies the installed Qt.?

------------------------------------------------------------------------------
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
Valgrind-users@...
https://lists.sourceforge.net/lists/listinfo/valgrind-users

From forum: Valgrind - Users

Looking up and calling functions in the target executable from an interception?

2009-12-06T09:45:01Z

Hi,
I'm starting to look at https://bugs.kde.org/show_bug.cgi?id=217615
(new/new[]/malloc mismatch detection when valgrinding win32 apps with wine).

Rather than replace the whole heap, I'd like to stick
with the wine system heap (which already is pretty
valgrind-friendly, and getting more so), and just override msvcrt's
implementations of new, new[], malloc, etc. with thin
shims that allocate a slightly larger block using
the win32 system heap (the one in kernel32,
which is below the one in msvcrt) and saves the
type of allocation in the extra space.

I have successfully intercepted msvcrt's malloc
in valgrind, but then I don't know how to look up
and call target functions inside the interceptor.
The functions I want to call ought to be easy to
look up from the loaded debug info, but I'm not
familiar enough with valgrind's symbol table stuff
to be able to do that straight off.

If anyone can supply a hint, that'd be welcome. In
the meantime I'll try to lurch along by linking replacement
functions into the target app instead of doing a shiny
interceptor in valgrind.
- Dan

------------------------------------------------------------------------------
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
Valgrind-users@...
https://lists.sourceforge.net/lists/listinfo/valgrind-users

From forum: Valgrind - Users

Unable to install valkyrie-1.4.0 on Ubuntu

2009-12-05T16:54:55Z

Hi,

Configure command of valkyrie fails with Qt related error.It seems configure command unable to detect the Qt sdk installed on my machine.

Qt 4.5.3 sdk installed in /opt/qtsdk-2009.04/qt and valgrind-3.4.1-Debian installed on the Ubuntu machine.Is it required to define Qt environment variables so that valkyrie identifies the installed Qt.?

configure.log is attached.

-Suresh.

[config.log]

This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by Valkyrie configure 1.4.0, which was generated by GNU Autoconf 2.61. Invocation command line was $ ./configure ## --------- ## ## Platform. ## ## --------- ## hostname = jackalope uname -m = i686 uname -r = 2.6.28-16-generic uname -s = Linux uname -v = #55-Ubuntu SMP Tue Oct 20 19:48:24 UTC 2009 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/sbin PATH: /usr/bin PATH: /sbin PATH: /bin PATH: /usr/games ## ----------- ## ## Core tests. ## ## ----------- ## configure:1827: checking for a BSD-compatible install configure:1883: result: /usr/bin/install -c configure:1894: checking whether build environment is sane configure:1937: result: yes configure:1965: checking for a thread-safe mkdir -p configure:2004: result: /bin/mkdir -p configure:2017: checking for gawk configure:2047: result: no configure:2017: checking for mawk configure:2033: found /usr/bin/mawk configure:2044: result: mawk configure:2055: checking whether make sets $(MAKE) configure:2076: result: yes configure:2284: checking for style of include used by make configure:2312: result: GNU configure:2392: checking for g++ configure:2408: found /usr/bin/g++ configure:2419: result: g++ configure:2450: checking for C++ compiler version configure:2457: g++ --version >&5 g++ (Ubuntu 4.3.3-5ubuntu4) 4.3.3 Copyright (C) 2008 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:2460: $? = 0 configure:2467: g++ -v >&5 Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.3.3-5ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) configure:2470: $? = 0 configure:2477: g++ -V >&5 g++: '-V' option must have argument configure:2480: $? = 1 configure:2503: checking for C++ compiler default output file name configure:2530: g++ conftest.cpp >&5 configure:2533: $? = 0 configure:2571: result: a.out configure:2588: checking whether the C++ compiler works configure:2598: ./a.out configure:2601: $? = 0 configure:2618: result: yes configure:2625: checking whether we are cross compiling configure:2627: result: no configure:2630: checking for suffix of executables configure:2637: g++ -o conftest conftest.cpp >&5 configure:2640: $? = 0 configure:2664: result: configure:2670: checking for suffix of object files configure:2696: g++ -c conftest.cpp >&5 configure:2699: $? = 0 configure:2722: result: o configure:2726: checking whether we are using the GNU C++ compiler configure:2755: g++ -c conftest.cpp >&5 configure:2761: $? = 0 configure:2778: result: yes configure:2783: checking whether g++ accepts -g configure:2813: g++ -c -g conftest.cpp >&5 configure:2819: $? = 0 configure:2918: result: yes configure:2943: checking dependency style of g++ configure:3034: result: gcc3 configure:3097: checking for gcc configure:3113: found /usr/bin/gcc configure:3124: result: gcc configure:3362: checking for C compiler version configure:3369: gcc --version >&5 gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3 Copyright (C) 2008 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3372: $? = 0 configure:3379: gcc -v >&5 Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.3.3-5ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) configure:3382: $? = 0 configure:3389: gcc -V >&5 gcc: '-V' option must have argument configure:3392: $? = 1 configure:3395: checking whether we are using the GNU C compiler configure:3424: gcc -c conftest.c >&5 configure:3430: $? = 0 configure:3447: result: yes configure:3452: checking whether gcc accepts -g configure:3482: gcc -c -g conftest.c >&5 configure:3488: $? = 0 configure:3587: result: yes configure:3604: checking for gcc option to accept ISO C89 configure:3678: gcc -c -g -O2 conftest.c >&5 configure:3684: $? = 0 configure:3707: result: none needed configure:3727: checking dependency style of gcc configure:3818: result: gcc3 configure:3839: checking how to run the C preprocessor configure:3879: gcc -E conftest.c configure:3885: $? = 0 configure:3916: gcc -E conftest.c conftest.c:10:28: error: ac_nonexistent.h: No such file or directory configure:3922: $? = 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME "Valkyrie" | #define PACKAGE_TARNAME "valkyrie" | #define PACKAGE_VERSION "1.4.0" | #define PACKAGE_STRING "Valkyrie 1.4.0" | #define PACKAGE_BUGREPORT "info@..." | #define PACKAGE "valkyrie" | #define VERSION "1.4.0" | /* end confdefs.h. */ | #include <ac_nonexistent.h> configure:3955: result: gcc -E configure:3984: gcc -E conftest.c configure:3990: $? = 0 configure:4021: gcc -E conftest.c conftest.c:10:28: error: ac_nonexistent.h: No such file or directory configure:4027: $? = 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME "Valkyrie" | #define PACKAGE_TARNAME "valkyrie" | #define PACKAGE_VERSION "1.4.0" | #define PACKAGE_STRING "Valkyrie 1.4.0" | #define PACKAGE_BUGREPORT "info@..." | #define PACKAGE "valkyrie" | #define VERSION "1.4.0" | /* end confdefs.h. */ | #include <ac_nonexistent.h> configure:4065: checking for X configure:4180: gcc -E conftest.c configure:4186: $? = 0 configure:4235: gcc -o conftest -g -O2 conftest.c -lX11 >&5 configure:4241: $? = 0 configure:4300: result: libraries , headers configure:4461: gcc -o conftest -g -O2 conftest.c -lX11 >&5 configure:4467: $? = 0 configure:4624: checking for gethostbyname configure:4680: gcc -o conftest -g -O2 conftest.c >&5 configure:4686: $? = 0 configure:4703: result: yes configure:4848: checking for connect configure:4904: gcc -o conftest -g -O2 conftest.c >&5 configure:4910: $? = 0 configure:4927: result: yes configure:4999: checking for remove configure:5055: gcc -o conftest -g -O2 conftest.c >&5 configure:5061: $? = 0 configure:5078: result: yes configure:5150: checking for shmat configure:5206: gcc -o conftest -g -O2 conftest.c >&5 configure:5212: $? = 0 configure:5229: result: yes configure:5310: checking for IceConnectionNumber in -lICE configure:5345: gcc -o conftest -g -O2 conftest.c -lICE >&5 configure:5351: $? = 0 configure:5369: result: yes configure:5384: checking for Qt configure:5588: gcc -o conftest -g -O2 conftest.c -lqt -lSM -lICE -lX11 -lXext -lXmu -lXt -lXi >&5 conftest.c:10:26: error: qapplication.h: No such file or directory conftest.c: In function 'main': conftest.c:17: error: 'QApplication' undeclared (first use in this function) conftest.c:17: error: (Each undeclared identifier is reported only once conftest.c:17: error: for each function it appears in.) conftest.c:17: error: expected ';' before 'app' configure:5594: $? = 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME "Valkyrie" | #define PACKAGE_TARNAME "valkyrie" | #define PACKAGE_VERSION "1.4.0" | #define PACKAGE_STRING "Valkyrie 1.4.0" | #define PACKAGE_BUGREPORT "info@..." | #define PACKAGE "valkyrie" | #define VERSION "1.4.0" | /* end confdefs.h. */ | #include <qapplication.h> | int | main () | { | | int argc; | char ** argv; | QApplication app(argc,argv); | | ; | return 0; | } Non-critical error, please neglect the above. configure:5635: gcc -o conftest -g -O2 conftest.c -lqt-mt -lSM -lICE -lX11 -lXext -lXmu -lXt -lXi >&5 conftest.c:10:26: error: qapplication.h: No such file or directory conftest.c: In function 'main': conftest.c:17: error: 'QApplication' undeclared (first use in this function) conftest.c:17: error: (Each undeclared identifier is reported only once conftest.c:17: error: for each function it appears in.) conftest.c:17: error: expected ';' before 'app' configure:5641: $? = 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME "Valkyrie" | #define PACKAGE_TARNAME "valkyrie" | #define PACKAGE_VERSION "1.4.0" | #define PACKAGE_STRING "Valkyrie 1.4.0" | #define PACKAGE_BUGREPORT "info@..." | #define PACKAGE "valkyrie" | #define VERSION "1.4.0" | /* end confdefs.h. */ | #include <qapplication.h> | int | main () | { | | int argc; | char ** argv; | QApplication app(argc,argv); | | ; | return 0; | } Non-critical error, please neglect the above. configure:5682: gcc -o conftest -g -O2 conftest.c -lqt-gl -lSM -lICE -lX11 -lXext -lXmu -lXt -lXi >&5 conftest.c:10:26: error: qapplication.h: No such file or directory conftest.c: In function 'main': conftest.c:17: error: 'QApplication' undeclared (first use in this function) conftest.c:17: error: (Each undeclared identifier is reported only once conftest.c:17: error: for each function it appears in.) conftest.c:17: error: expected ';' before 'app' configure:5688: $? = 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME "Valkyrie" | #define PACKAGE_TARNAME "valkyrie" | #define PACKAGE_VERSION "1.4.0" | #define PACKAGE_STRING "Valkyrie 1.4.0" | #define PACKAGE_BUGREPORT "info@..." | #define PACKAGE "valkyrie" | #define VERSION "1.4.0" | /* end confdefs.h. */ | #include <qapplication.h> | int | main () | { | | int argc; | char ** argv; | QApplication app(argc,argv); | | ; | return 0; | } Non-critical error, please neglect the above. configure:5754: gcc -o conftest -g -O2 conftest.c -lqt-mt -lSM -lICE -lX11 -lXext -lXmu -lXt -lXi >&5 conftest.c:10:26: error: qapplication.h: No such file or directory conftest.c: In function 'main': conftest.c:17: error: 'QApplication' undeclared (first use in this function) conftest.c:17: error: (Each undeclared identifier is reported only once conftest.c:17: error: for each function it appears in.) conftest.c:17: error: expected ';' before 'app' configure:5760: $? = 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME "Valkyrie" | #define PACKAGE_TARNAME "valkyrie" | #define PACKAGE_VERSION "1.4.0" | #define PACKAGE_STRING "Valkyrie 1.4.0" | #define PACKAGE_BUGREPORT "info@..." | #define PACKAGE "valkyrie" | #define VERSION "1.4.0" | /* end confdefs.h. */ | #include <qapplication.h> | int | main () | { | | int argc; | char ** argv; | QApplication app(argc,argv); | | ; | return 0; | } configure:5877: result: no configure:5988: error: Cannot build without QT. ## ---------------- ## ## Cache variables. ## ## ---------------- ## ac_cv_c_compiler_gnu=yes ac_cv_cxx_compiler_gnu=yes ac_cv_env_CCC_set= ac_cv_env_CCC_value= ac_cv_env_CC_set= ac_cv_env_CC_value= ac_cv_env_CFLAGS_set= ac_cv_env_CFLAGS_value= ac_cv_env_CPPFLAGS_set= ac_cv_env_CPPFLAGS_value= ac_cv_env_CPP_set= ac_cv_env_CPP_value= ac_cv_env_CXXFLAGS_set= ac_cv_env_CXXFLAGS_value= ac_cv_env_CXX_set= ac_cv_env_CXX_value= ac_cv_env_LDFLAGS_set= ac_cv_env_LDFLAGS_value= ac_cv_env_LIBS_set= ac_cv_env_LIBS_value= ac_cv_env_XMKMF_set= ac_cv_env_XMKMF_value= ac_cv_env_build_alias_set= ac_cv_env_build_alias_value= ac_cv_env_host_alias_set= ac_cv_env_host_alias_value= ac_cv_env_target_alias_set= ac_cv_env_target_alias_value= ac_cv_func_connect=yes ac_cv_func_gethostbyname=yes ac_cv_func_remove=yes ac_cv_func_shmat=yes ac_cv_have_x='have_x=yes ac_x_includes='\'''\'' ac_x_libraries='\'''\''' ac_cv_lib_ICE_IceConnectionNumber=yes ac_cv_objext=o ac_cv_path_install='/usr/bin/install -c' ac_cv_path_mkdir=/bin/mkdir ac_cv_prog_AWK=mawk ac_cv_prog_CPP='gcc -E' ac_cv_prog_ac_ct_CC=gcc ac_cv_prog_ac_ct_CXX=g++ ac_cv_prog_cc_c89= ac_cv_prog_cc_g=yes ac_cv_prog_cxx_g=yes ac_cv_prog_make_make_set=yes am_cv_CC_dependencies_compiler_type=gcc3 am_cv_CXX_dependencies_compiler_type=gcc3 bnv_cv_have_qt=have_qt=no ## ----------------- ## ## Output variables. ## ## ----------------- ## ACLOCAL='${SHELL} /home/manchi/CppProjects/valgrind/valkyrie-1.4.0/missing --run aclocal-1.10' ALLOCA='' AMDEPBACKSLASH='\' AMDEP_FALSE='#' AMDEP_TRUE='' AMTAR='${SHELL} /home/manchi/CppProjects/valgrind/valkyrie-1.4.0/missing --run tar' AUTOCONF='${SHELL} /home/manchi/CppProjects/valgrind/valkyrie-1.4.0/missing --run autoconf' AUTOHEADER='${SHELL} /home/manchi/CppProjects/valgrind/valkyrie-1.4.0/missing --run autoheader' AUTOMAKE='${SHELL} /home/manchi/CppProjects/valgrind/valkyrie-1.4.0/missing --run automake-1.10' AWK='mawk' CC='gcc' CCDEPMODE='depmode=gcc3' CFLAGS='-g -O2' CPP='gcc -E' CPPFLAGS='' CXX='g++' CXXDEPMODE='depmode=gcc3' CXXFLAGS='-g -O2' CYGPATH_W='echo' DEFS='' DEPDIR='.deps' ECHO_C='' ECHO_N='-n' ECHO_T='' EGREP='' EXEEXT='' GREP='' INSTALL_DATA='${INSTALL} -m 644' INSTALL_PROGRAM='${INSTALL}' INSTALL_SCRIPT='${INSTALL}' INSTALL_STRIP_PROGRAM='$(install_sh) -c -s' LDFLAGS='' LIBOBJS='' LIBS='' LN_S='' LTLIBOBJS='' MAKEINFO='${SHELL} /home/manchi/CppProjects/valgrind/valkyrie-1.4.0/missing --run makeinfo' OBJEXT='o' PACKAGE='valkyrie' PACKAGE_BUGREPORT='info@...' PACKAGE_NAME='Valkyrie' PACKAGE_STRING='Valkyrie 1.4.0' PACKAGE_TARNAME='valkyrie' PACKAGE_VERSION='1.4.0' PATH_SEPARATOR=':' PERL='' QT_CXXFLAGS='' QT_DIR='' QT_LIBS='' QT_MOC='' QT_UIC='' RANLIB='' SET_MAKE='' SHELL='/bin/bash' STRIP='' VALGRIND='' VERSION='1.4.0' VK_EDITOR='' XMKMF='' X_CFLAGS='' X_EXTRA_LIBS='' X_LIBS='' X_PRE_LIBS=' -lSM -lICE' ac_ct_CC='gcc' ac_ct_CXX='g++' am__fastdepCC_FALSE='#' am__fastdepCC_TRUE='' am__fastdepCXX_FALSE='#' am__fastdepCXX_TRUE='' am__include='include' am__isrc='' am__leading_dot='.' am__quote='' am__tar='${AMTAR} chof - "$$tardir"' am__untar='${AMTAR} xf -' bindir='${exec_prefix}/bin' build_alias='' datadir='${datarootdir}' datarootdir='${prefix}/share' docdir='${datarootdir}/doc/${PACKAGE_TARNAME}' dvidir='${docdir}' exec_prefix='NONE' host_alias='' htmldir='${docdir}' includedir='${prefix}/include' infodir='${datarootdir}/info' install_sh='$(SHELL) /home/manchi/CppProjects/valgrind/valkyrie-1.4.0/install-sh' libdir='${exec_prefix}/lib' libexecdir='${exec_prefix}/libexec' localedir='${datarootdir}/locale' localstatedir='${prefix}/var' mandir='${datarootdir}/man' mkdir_p='/bin/mkdir -p' oldincludedir='/usr/include' pdfdir='${docdir}' prefix='NONE' program_transform_name='s,x,x,' psdir='${docdir}' sbindir='${exec_prefix}/sbin' sharedstatedir='${prefix}/com' sysconfdir='${prefix}/etc' target_alias='' ## ----------- ## ## confdefs.h. ## ## ----------- ## #define PACKAGE_NAME "Valkyrie" #define PACKAGE_TARNAME "valkyrie" #define PACKAGE_VERSION "1.4.0" #define PACKAGE_STRING "Valkyrie 1.4.0" #define PACKAGE_BUGREPORT "info@..." #define PACKAGE "valkyrie" #define VERSION "1.4.0" configure: exit 1

------------------------------------------------------------------------------
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
Valgrind-users@...
https://lists.sourceforge.net/lists/listinfo/valgrind-users

From forum: Valgrind - Users

Re: "fatal error: unsupported CPU" on Via C7 Esther processor

2009-12-05T02:55:14Z

Julian Seward wrote:

>> Trying to avoid doing real work, I searched for "unsupported CPU" and
>> found it in coregrind/m_main.c. I then found VG_(machine_get_hwcaps)() in
>> m_machine.c. Putting a few VG_(printf)() calls into this routine, I found
>> that it fails this test:
>>
>> /* cmpxchg8b is a minimum requirement now; if we don't have it we
>> must simply give up. But all CPUs since Pentium-I have it, so
>> that doesn't seem like much of a restriction. */
>> have_cx8 = (edx & (1<<8)) != 0; /* True => have cmpxchg8b */
>> if (!have_cx8)
>> return False;
>>
>> Interestingly, /proc/cpuinfo does not show "cx8" on my machines, while it
>> does on yours. I didn't think my CPU was that old, since it runs at 1.2
>> GHz (I bought the machines in late 2006). Looks like I am out of luck on
>> these two machines. Given the comment in the source code here, I doubt
>> very much that provisions would be made to support this CPU. :-)
>>
>
> It may be that the CPU does support cmpxchg8b but doesn't say it does.
> Try compiling and running the program none/tests/x86/cmpxchg8b.c in the
> 3.5.0 tree, and see if it runs natively OK (without SIGILL). If yes
> then comment out the relevant test in VG_(machine_get_hwcaps)().
>
> J
>
>

I got the following output from the program, which looks correct if my
understanding of CMPXCHG8B is correct (last time I wrote ASM, the 386
was still very new!):

0x22222222 0x44444444 0x33333333 0x11111111 0x246 0x3333333344444444
0x22222223 0x44444444 0x33333333 0x11111111 0x206 0x1111111122222223
0x22222222 0x44444444 0x33333333 0x11111112 0x206 0x1111111222222222
0x77777777 0x44444444 0x33333333 0x66666666 0x206 0x6666666677777777

It didn't core dump, anyway, and "./vg-in-place date" runs to completion
after I comment out those lines in VG_(machine_get_hwcaps)(). So I
guess that's a good thing. But it's nearly 3 A.M. here in California
and I could be wrong. ;-)

It is a little surprising that the C7 Esther core doesn't report that
instruction, but the Linux kernel has special compilation flags for this
CPU because it claims to be a 686 compatible processor yet doesn't
implement all of the instructions of a real Pentium II. Maybe this is a
similar issue (though harmless for most software packages because they
work around it).

Thanks for your help.

------------------------------------------------------------------------------
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
Valgrind-users@...
https://lists.sourceforge.net/lists/listinfo/valgrind-users

From forum: Valgrind - Users

Re: "fatal error: unsupported CPU" on Via C7 Esther processor

2009-12-05T01:43:47Z

> Trying to avoid doing real work, I searched for "unsupported CPU" and
> found it in coregrind/m_main.c. I then found VG_(machine_get_hwcaps)() in
> m_machine.c. Putting a few VG_(printf)() calls into this routine, I found
> that it fails this test:
>
>       /* cmpxchg8b is a minimum requirement now; if we don't have it we
>          must simply give up. But all CPUs since Pentium-I have it, so
>          that doesn't seem like much of a restriction. */
>       have_cx8 = (edx & (1<<8)) != 0; /* True => have cmpxchg8b */
>       if (!have_cx8)
>          return False;
>
> Interestingly, /proc/cpuinfo does not show "cx8" on my machines, while it
> does on yours. I didn't think my CPU was that old, since it runs at 1.2
> GHz (I bought the machines in late 2006). Looks like I am out of luck on
> these two machines. Given the comment in the source code here, I doubt
> very much that provisions would be made to support this CPU. :-)

It may be that the CPU does support cmpxchg8b but doesn't say it does.
Try compiling and running the program none/tests/x86/cmpxchg8b.c in the
3.5.0 tree, and see if it runs natively OK (without SIGILL). If yes
then comment out the relevant test in VG_(machine_get_hwcaps)().

J

------------------------------------------------------------------------------
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
Valgrind-users@...
https://lists.sourceforge.net/lists/listinfo/valgrind-users

From forum: Valgrind - Users

Re: "fatal error: unsupported CPU" on Via C7 Esther processor

2009-12-04T17:53:19Z

David Chapman wrote:

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.  :-(

Trying to avoid doing real work, I searched for "unsupported CPU" and found it in coregrind/m_main.c. I then found VG_(machine_get_hwcaps)() in m_machine.c. Putting a few VG_(printf)() calls into this routine, I found that it fails this test:

     /* cmpxchg8b is a minimum requirement now; if we don't have it we
        must simply give up. But all CPUs since Pentium-I have it, so
        that doesn't seem like much of a restriction. */
     have_cx8 = (edx & (1<<8)) != 0; /* True => have cmpxchg8b */
     if (!have_cx8)
        return False;

Interestingly, /proc/cpuinfo does not show "cx8" on my machines, while it does on yours. I didn't think my CPU was that old, since it runs at 1.2 GHz (I bought the machines in late 2006). Looks like I am out of luck on these two machines. Given the comment in the source code here, I doubt very much that provisions would be made to support this CPU. :-)

At least I have dual-core and quad-core Athlons that I can also do development on...

------------------------------------------------------------------------------
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
Valgrind-users@...
https://lists.sourceforge.net/lists/listinfo/valgrind-users

From forum: Valgrind - Users

(unchanged) 2009-12-04 02:23:19 EST nightly build (cellbuzz-native, cellbuzz, ppc64, Fedora 7, native)

2009-12-04T00:51:52Z

Nightly build on cellbuzz-native ( cellbuzz, ppc64, Fedora 7, native )
Started at 2009-12-04 02:23:19 EST
Ended at 2009-12-04 03:51:46 EST
Results unchanged from 24 hours ago

Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... done

Regression test results follow

== 449 tests, 45 stderr failures, 10 stdout failures, 0 post failures ==
memcheck/tests/deep_templates (stdout)
memcheck/tests/leak-cases-full (stderr)
memcheck/tests/leak-cases-summary (stderr)
memcheck/tests/leak-cycle (stderr)
memcheck/tests/linux/timerfd-syscall (stdout)
memcheck/tests/linux-syscalls-2007 (stderr)
memcheck/tests/origin5-bz2 (stderr)
memcheck/tests/partiallydefinedeq (stderr)
memcheck/tests/varinfo1 (stderr)
memcheck/tests/varinfo2 (stderr)
memcheck/tests/varinfo3 (stderr)
memcheck/tests/varinfo4 (stderr)
memcheck/tests/varinfo5 (stderr)
memcheck/tests/varinfo6 (stderr)
memcheck/tests/wrap8 (stdout)
memcheck/tests/wrap8 (stderr)
none/tests/empty-exe (stderr)
none/tests/linux/mremap (stderr)
none/tests/ppc32/jm-fp (stdout)
none/tests/ppc32/jm-vmx (stdout)
none/tests/ppc32/round (stdout)
none/tests/ppc32/test_gx (stdout)
none/tests/ppc64/jm-fp (stdout)
none/tests/ppc64/jm-vmx (stdout)
none/tests/ppc64/round (stdout)
none/tests/shell_valid2 (stderr)
none/tests/shell_valid3 (stderr)
none/tests/shell_zerolength (stderr)
helgrind/tests/hg05_race2 (stderr)
helgrind/tests/tc06_two_races_xml (stderr)
helgrind/tests/tc22_exit_w_lock (stderr)
helgrind/tests/tc23_bogus_condwait (stderr)
drd/tests/tc23_bogus_condwait (stderr)
exp-ptrcheck/tests/bad_percentify (stderr)
exp-ptrcheck/tests/base (stderr)
exp-ptrcheck/tests/ccc (stderr)
exp-ptrcheck/tests/fp (stderr)
exp-ptrcheck/tests/globalerr (stderr)
exp-ptrcheck/tests/hackedbz2 (stderr)
exp-ptrcheck/tests/hp_bounds (stderr)
exp-ptrcheck/tests/hp_dangle (stderr)
exp-ptrcheck/tests/hsg (stderr)
exp-ptrcheck/tests/justify (stderr)
exp-ptrcheck/tests/partial_bad (stderr)
exp-ptrcheck/tests/partial_good (stderr)
exp-ptrcheck/tests/preen_invars (stderr)
exp-ptrcheck/tests/pth_create (stderr)
exp-ptrcheck/tests/pth_specific (stderr)
exp-ptrcheck/tests/realloc (stderr)
exp-ptrcheck/tests/stackerr (stderr)
exp-ptrcheck/tests/strcpy (stderr)
exp-ptrcheck/tests/supp (stderr)
exp-ptrcheck/tests/tricky (stderr)
exp-ptrcheck/tests/unaligned (stderr)
exp-ptrcheck/tests/zero (stderr)

------------------------------------------------------------------------------
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-developers mailing list
Valgrind-developers@...
https://lists.sourceforge.net/lists/listinfo/valgrind-developers

diffs.gz (28K) Download Attachment

Nabble - Valgrind

Re: Unable to install valkyrie-1.4.0 on Ubuntu

Looking up and calling functions in the target executable from an interception?

Unable to install valkyrie-1.4.0 on Ubuntu

Re: "fatal error: unsupported CPU" on Via C7 Esther processor

Re: "fatal error: unsupported CPU" on Via C7 Esther processor

Re: "fatal error: unsupported CPU" on Via C7 Esther processor

(unchanged) 2009-12-04 02:23:19 EST nightly build (cellbuzz-native, cellbuzz, ppc64, Fedora 7, native)

Valgrind 3.5.0 on SuSE 8

(unchanged) 2009-12-04 09:06:00 MSK nightly build (mcgrind, Darwin 9.7.0 i386)

(unchanged) 2009-12-04 03:05:06 GMT nightly build (lloyd, x86_64, Fedora 7)

(unchanged) 2009-12-04 03:10:06 GMT nightly build (mg, x86_64, Fedora 9)

Re: "fatal error: unsupported CPU" on Via C7 Esther processor

valgrind: r10964 - trunk/coregrind/m_debuginfo

vex: r1938 - trunk/priv

valgrind: r10963 - trunk/coregrind/m_debuginfo

Re: "fatal error: unsupported CPU" on Via C7 Esther processor

(unchanged) 2009-12-03 09:06:00 MSK nightly build (mcgrind, Darwin 9.7.0 i386)

(unchanged) 2009-12-03 02:00:05 EST nightly build (cellbuzz-native, cellbuzz, ppc64, Fedora 7, native)

(unchanged) 2009-12-03 03:05:05 GMT nightly build (lloyd, x86_64, Fedora 7)

(unchanged) 2009-12-03 03:10:09 GMT nightly build (mg, x86_64, Fedora 9)

"fatal error: unsupported CPU" on Via C7 Esther processor

valgrind: r10962 - trunk/coregrind/m_syswrap

pub_tool_basics.h: Issue compiling on AIX 5

Re: memcheck behaviour in random failure of an open mpi based code.

(unchanged) 2009-12-02 09:06:00 MSK nightly build (mcgrind, Darwin 9.7.0 i386)

2009-12-02 02:00:08 EST nightly build (cellbuzz-native, cellbuzz, ppc64, Fedora 7, native)

(unchanged) 2009-12-02 03:05:04 GMT nightly build (lloyd, x86_64, Fedora 7)

(unchanged) 2009-12-02 03:10:04 GMT nightly build (mg, x86_64, Fedora 9)

vex: r1937 - branches/ARM/priv

Re: memcheck behaviour in random failure of an open mpi based code.

valgrind: r10961 - branches/ARM/coregrind/m_replacemalloc

valgrind: r10960 - trunk/coregrind/m_syswrap

(unchanged) 2009-12-01 09:06:00 MSK nightly build (mcgrind, Darwin 9.7.0 i386)

(unchanged) 2009-12-01 02:23:30 EST nightly build (cellbuzz-native, cellbuzz, ppc64, Fedora 7, native)

(unchanged) 2009-12-01 03:05:05 GMT nightly build (lloyd, x86_64, Fedora 7)