Hi,

On Fri, 12 Oct 2007, Shawn O. Pearce wrote:

quoted text
> Shun Kei Leung <kevinlsk@gmail.com> wrote:
> > Program received signal EXC_BAD_ACCESS, Could not access memory.
> > Reason: KERN_INVALID_ADDRESS at address: 0x64617469
> > in_window (win=0x5004d0, offset=3501) at sha1_file.c:701
> > 701             off_t win_off = win->offset;
> ...
> > (gdb) print win
> >  = (struct pack_window *) 0x5004d0
> > (gdb) print *win
> >  = {
> >   next = 0x64617461,
> >   base = 0x20333936 <Address 0x20333936 out of bounds>,
> >   offset = 22523564414626158,
> >   len = 1685026675,
> >   last_used = 795894075,
> >   inuse_cnt = 0
> > }
> 
> Wow.  There's no way that struct pack_window is valid anymore.
>
> [...] 
>
> This looks like it is memory corruption (e.g. someone overwriting a 
> free'd segment), but that sort of memory corruption is very hard to 
> track down.

I found valgrind invaluable to find such errors.

Ciao,
Dscho

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html