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

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

Hi;

2010/7/29 Julian Seward <js...@ac...>

>
> > 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
>
> Urr, that's strange.  That segfault is within 15 instructions
> of the process startup.  Try single stepping from _start, which
> is defined at m_main.c:2984.  It takes control from the
> kernel, switches stacks, and calls the routine that segfaults.
> Without being able to reproduce this, my changes of figuring out
> what's going wrong are essentially zero, so you'll have to do it.
>
> See also the comment at m_main.c:2942.  That might be related.


Trying to set a breakpoint in m_main.c:2984 does not work, looks like gdb
cannot set a breakpoint inside inline ASM. I will try to figure whats wrong
and will report back anything interesting.

Regards,
ismail


>