From: John R. <jr...@bi...> - 2012-01-23 21:59:13
|
On 01/23/2012 01:02 PM, Daniel Mierswa wrote: > On 23.01.2012 21:46, John Reiser wrote: >> and then perhaps do some matching on the low 12 bits (0xFFF) of the address: >> 0x44143D0 ==> any address ending in 0x3D0. > 0x000143d0 <+880>: vmovd 0x4(%eax),%xmm0 >> In 32-bit mode, hardware opcode 0xC5 is 'LDS' (Load Data Segment register), >> which compiled software does not use. > what exactly does that mean now regarding my problem? is glibc broken? valgrind? :D Probably there is an unexpected interaction between the code in glibc which does processor detection using CPUID (etc.), and the code in valgrind which delivers "synthetic" results for CPUID. Both valgrind and glibc might need to be more robust. Look in the disassembly for 'cpuid'. File a bug report against valgrind at https://bugs.kde.org/ . Include the complete disassembly of _dl_sysdep_start, and the name and version of your Linux and glibc. -- |