I am attempting to build Valgrind locally and notice that the output from
running configure is:
Maximum build arch: amd64
Primary build arch: amd64
Secondary build arch: x86
Build OS: darwin
Primary build target: AMD64_DARWIN
Secondary build target: X86_DARWIN
On Thu, 2012-07-12 at 14:42 -0700, Jacob Goldstein wrote:
Primary build arch: amd64
Secondary build arch: x86
I'm running on a MacBook Pro with an Intel i7 CPU (running OS X
10.7.4), so I'm not sure why the primary build arch is amd64.
amd64 indicates it is the intel
Hello,
I have been attempting to build and run WebKit LayoutTests under Valgrind,
without much success. WebKit is being built with Xcode. It works as expected
with Xcode 3.x, which uses GCC, but not with Xcode 4.x, which uses CLANG. A
simple program works fine with each, but when I build
Ah, ok, thanks for the clarification.
On 7/12/12 2:52 PM, Philippe Waroquiers philippe.waroqui...@skynet.be
wrote:
On Thu, 2012-07-12 at 14:42 -0700, Jacob Goldstein wrote:
Primary build arch: amd64
Secondary build arch: x86
I'm running on a MacBook Pro with an Intel i7 CPU
Maximum build arch: amd64
Primary build arch: amd64
Secondary build arch: x86
Build OS: darwin
Primary build target: AMD64_DARWIN
Secondary build target: X86_DARWIN
Platform variant: vanilla
Primary -DVGPV string:
On Wed, Jul 11, 2012 at 10:13 PM, Tanmay Mohapatra tanma...@hotmail.com wrote:
Thanks Pat.
Here's the output of otool -v -t check
Is this what is required?
Do let me know if I need to disassemble in some other way.
Looks like the offending code is in a shared library (?)
Maybe try gdb
This doesn't really help you, but ...
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.
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
Julian and John - thanks very much for your replies, I really appreciate
your help.
--trace-syscalls=yes worked. I got a lot of SYSCALLs.
Let me provide a little more background in case this helps shed some light
on the situation.
I'm running on two different machines:
1) MacBook Pro / Intel
I'm running on two different machines:
1) MacBook Pro / Intel i7 / OS X 10.7.4 / Xcode 4.3.1 (which uses
LLVM/CLANG)
2) iMac / Intel Core 2 Duo / OS X 10.6.8 / Xcode 3.2 (which uses GCC)
I'm running valgrind-3.8.0.SVN that I built locally.
I get different results on each machine.
10 matches
Mail list logo