Re: [Valgrind-users] Valgrind trunk crashes on Mac OSX 10.6 64bit

[İsmail D. <is...@na...>]

On Thu, Jul 29, 2010 at 10:41 AM, İsmail Dönmez <is...@na...> wrote:

> Hi Julian;
>
> On Thu, Jul 29, 2010 at 10:41 AM, Julian Seward <js...@ac...> wrote:
>
>> On Thursday, July 29, 2010, İsmail Dönmez wrote:
>> > Hello;
>> >
>> > I was happy to hear Valgrind is ported darwin/amd64, so I grabbed the
>> > sources from trunk and compiled it. But it crashes on startup, here are
>> > some details;
>>
>> I am surprised to hear this.  I have been using trunk on
>> Mac OSX 10.6 64bit for a while now and it successfully runs a
>> multi-million-lines-of-C++ application.  I believe others also
>> use it successfully.
>>
>>
And here is the real reason it crashes;

[~]> gdb /usr/local/lib/valgrind/memcheck-amd64-darwin
GNU gdb 6.3.50-20050815 (Apple version gdb-1502) (Thu Jul  8 12:27:19 UTC
2010)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin"...
(gdb) run
Starting program: /usr/local/lib/valgrind/memcheck-amd64-darwin

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000134000000
_start_in_C_darwin (pArgc=0x134000000) at m_main.c:3033
3033   Int     argc = *(Int *)pArgc;  // not pArgc[0] on LP64
(gdb) print pArgc
$1 = (UWord *) 0x134000000
(gdb) print *pArgc
Cannot access memory at address 0x134000000

Regards,
ismail