https://bugs.kde.org/show_bug.cgi?id=250799
<https://bugs.kde.org/show_bug.cgi?id=250799>
On Sep 9, 2010, at 6:08 PM, Julian Seward wrote:
On Thursday, September 09, 2010, Thomas Reilly wrote:
MacOS 10.6, valgrind-svn from a couple weeks ago.
vex x86->IR: unhandled instruction bytes: 0x66 0xF 0xBF 0x44
==880== valgrind: Unrecognised instruction at address 0x307dab.
...
==880== Process terminating with default action of signal 4 (SIGILL)
==880== Illegal opcode at address 0x307DAB
==880== at 0x307DAB: frexp$fenv_access_off (in
/usr/lib/libSystem.B.dylib)
Actual instruction:
0x97c42dab <frexp$fenv_access_off+107>: movsww 0x8(%esp),%ax
That sounds really bizarre. What's wrong with plain "movw 0x8(%esp), %ax"
I wonder.
I see lots of SIGILL bugs in the bugbase but none for this
function/instruction. Should I log a new bug?
Yes, pls do.
J
--------------------------------------------------------------------------
---- This SF.net<http://SF.net> Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Valgrind-users mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/valgrind-users
------------------------------------------------------------------------------
Automate Storage Tiering Simply
Optimize IT performance and efficiency through flexible, powerful,
automated storage tiering capabilities. View this brief to learn how
you can reduce costs and improve performance.
http://p.sf.net/sfu/dell-sfdev2dev
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
