Re: [Valgrind-users] "retq" is an unhandled instruction?

[Julian S. <js...@ac...>]

I just committed a fix (vex r2255).

J

On Thursday, February 16, 2012, Tom Hughes wrote:
> On 16/02/12 02:26, Patrick J. LoPresti wrote:
> > Disassembly of myApp leading up to 0x1FF07B5:
> >     0x1ff07aa<__intel_get_new_mem_ops_cpuid+26>:        mov   
> >     %edx,0xc(%r9) 0x1ff07ae<__intel_get_new_mem_ops_cpuid+30>:       
> >     pop    %rdx 0x1ff07af<__intel_get_new_mem_ops_cpuid+31>:        pop 
> >       %rcx 0x1ff07b0<__intel_get_new_mem_ops_cpuid+32>:        pop   
> >     %rbx 0x1ff07b1<__intel_get_new_mem_ops_cpuid+33>:        pop    %rax
> >     0x1ff07b2<__intel_get_new_mem_ops_cpuid+34>:        mov    %r8d,%eax
> >     0x1ff07b5<__intel_get_new_mem_ops_cpuid+37>:        retq   $0x0
> > 
> > Is this the correct forum for reporting bugs in the development version?
> 
> Well the bug tracker is probably better, but it's already done:
> 
> https://bugs.kde.org/show_bug.cgi?id=292430
> 
> Tom