On Sat, Oct 13, 2007 at 03:34:07AM +0000, Shawn O. Pearce wrote:
quoted text
> "Shawn O. Pearce" <spearce@spearce.org> wrote:
> > Shun Kei Leung <kevinlsk@gmail.com> wrote:
> > > I am using git 1.5.3.4.206.g58ba4-dirty on Mac OS X 10.4.
> ....
> > > Program received signal EXC_BAD_ACCESS, Could not access memory.
> > > Reason: KERN_INVALID_ADDRESS at address: 0x64617469
> ....
> > 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.
>=20
> OK, so the version you have (58ba4) is the latest fast-import after
> the strbuf.c series went in.  The one immediately before that series
> was 4bf538 and is probably actually stable.
>=20
> So I wonder, can you test 4bf538 and then if it is good bisect
> between those two commits?  There must be a memory corruption
> introduced by one of the strbuf changes...

  Gasp, if you get the offending sha1 commit, don't forget to Cc: me.

--=20
=C2=B7O=C2=B7  Pierre Habouzit
=C2=B7=C2=B7O                                                madcoder@debia=
n.org
OOO                                                http://www.madism.org