On Tue, 24 Jun 2008, Teemu Likonen wrote: > Jeff King wrote (2008-06-24 12:40 -0400): > > > On Tue, Jun 24, 2008 at 04:04:57PM +0300, Teemu Likonen wrote: > > > > > With the current "master" branch version (29b0d0191) I get > > > segmentation fault when trying to clone a git repo with http > > > protocol. Tried a couple of times and it's always reproducible. You > > > can test with the following repository (about 5.5 MB): > > > > > > git clone http://www.iki.fi/tlikonen/voikko.git > > > > I can't reproduce the segfault here. > > > > > I also build git from the tag v1.5.6 and it seems to work fine, so > > > I guess the bug was introduced after 1.5.6. > > > > That sounds like an excellent opportunity to learn about git-bisect. > > Can you try bisecting the bug and reporting back the problematic > > commit? > > Indeed. I have now officially bisected the problem and the first bad or > problematic commit is 8eca0b47 "implement some resilience against pack > corruptions" (hence Cc to Nicolas, the author). This is always > reproducible in my Debian 4.0 box. I'm trying to reproduce your segfault with current master (v1.5.6-56-g29b0d01) but I just can't. Can you provide a gdb backtrace of the segfault? What my patch does is to return NULL in all cases when an object exists but can't be read instead of dying. So if some user of read_sha1_file() is not checking for a returned null pointer then a null pointer dereference is most likely. Note that read_sha1_file() could have returned NULL even before my patch, but not necessarily in all cases. Nicolas -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
