> I'm running on a MacBook Pro with an Intel i7 CPU, so I'm not sure why the > primary build arch is amd64.
Because the best [5-character] name of the 64-bit x86 architecture is amd64. AMD beat the pants off Intel in that round of the architecture wars. > > The crash when running a WebKit test under Valgrind looks like the following > (some output has been removed): > > ---- Output ----- > ==21326== Memcheck, a memory error detector > ==21326== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. > ==21326== Using Valgrind-3.8.0.SVN and LibVEX; rerun with -h for copyright > info > ==21326== Command: /Users/jacobg/WebKit/WebKitBuild/Debug/DumpRenderTree - > ==21326== > > UNKNOWN __pthread_sigmask is unsupported. This warning will not be repeated. > vex amd64->IR: unhandled instruction bytes: 0xF 0xB 0x55 0x48 0x89 0xE5 0x41 > 0x56 > ==21326== valgrind: Unrecognised instruction at address 0x9167b8c. 0xF 0xB is 'ud2', the official two-byte "undefined opcode". The app has given up, and 'ud2' is an OS-independent way to guarantee an abort. (It's an infuriating bug that valgrind pretends not to know about 'ud2'.) The "real error" happened some time ago. To help find it, please re-run: valgrind --trace-system-calls=yes .../DumpRenderTree -- ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
