The gdbserver is a great new feature but I am having trouble getting it to stop
on the desired error.
If I have previously run valgrind (eg. overnight) and have the output, I can't
seem to determine the correct error count to cause a subsequent run to stop at
a particular error. The count of
Hi All,
I am trying to use Valgrind on OS X 10.7.3, and when I try to start a Cocoa
application, it always crashes at the following point:
vex amd64-IR: unhandled instruction bytes: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8
0x6A
==71202== valgrind: Unrecognised instruction at address 0x3945c0b.
On 2/9/2012 6:55 AM, Istvan Csanady wrote:
Hi All,
I am trying to use Valgrind on OS X 10.7.3, and when I try to start a Cocoa
application, it always crashes at the following point:
vex amd64-IR: unhandled instruction bytes: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8
0x6A
That looks like a variant
On 09/02/12 13:00, Eliot Moss wrote:
0x66 0x0F 0x3A 0xDF appears to be AESKEYGENASSIST.
Someone else will have to address that (if at all).
There's a bug for that already:
https://bugs.kde.org/show_bug.cgi?id=290655
Tom
--
Tom Hughes (t...@compton.nu)
http://compton.nu/
On Thu, Feb 9, 2012 at 5:00 PM, Eliot Moss m...@cs.umass.edu wrote:
I was wrong :-( ...
0x66 0x0F 0x3A 0xDF appears to be AESKEYGENASSIST.
Someone else will have to address that (if at all).
Sorry ... Eliot
There used to be a bug about incorrect declaration of AESKEYGENASSIST:
On 02/09/2012 03:50 AM, Istvan Csanady wrote:
vex amd64-IR: unhandled instruction bytes: 0x66 0xF 0x3A 0xDF 0xD1 0x1 0xE8
0x6A
Any help is greatly appreciated.
Such as, RTFM? It's even a FAQ!!
Begin at http://valgrind.org . Notice Documentation in the sidebar.
Click on FAQ.
On Thu, 2012-02-09 at 17:47 +0400, Alexander Potapenko wrote:
under Valgrind on your machine?
If it returns 0, it means that the code you're running is incorrectly
assuming AES support on the CPU (this is still a reason to fix
AESKEYGENASSIST)
Otherwise cpuid is broken under Valgrind.
at runtime if AES is supported or not (e.g. if this is checked at
installation time and different executable is installed depending on
this install check, then no luck (until Valgrind supports the AES
instructions).
Yeah, I agree with that analysis. The failing instruction is in a
system
Hi all,
I tried to run a win32 application under valgrind+wine on a gentoo x86
installation.
Sadly this failed on an internal error like in
https://bugs.kde.org/show_bug.cgi?id=275673
The error looks like this part from the bug:
strace.txt:61324:[pid 2563] pipe([20, 21]) = 0
On 09/02/12 20:36, Matthias Schwarzott wrote:
The attached patch applies against valgrind svn revision 12373.
Tested on a Gentoo amd64 installation built for 64bit and also built for
32bit (with --enable-only32bit).
Please open a bug in the bug tracker and attach your patch to it so that
it
FYI: I am busy working on implementing the AES instructions. Not very
advanced yet, but I guess it should arrive in the coming weeks.
Philippe, it is great that you are working on this, would be very useful
for the project I am working on. Unfortunately I am not qualified to help,
but hope your
11 matches
Mail list logo
