Guido Ostkamp <git@xxxxxxxxxxxxxxxxxxx> writes: > On Tue, 15 Sep 2009, Junio C Hamano wrote: > >> Please try this patch, which I have been preparing for later pushout. >> >> From: Junio C Hamano <gitster@xxxxxxxxx> >> Date: Mon, 14 Sep 2009 14:48:15 -0700 >> Subject: [PATCH] http.c: avoid freeing an uninitialized pointer >> >> An earlier 59b8d38 (http.c: remove verification of remote packs) left >> the variable "url" uninitialized; "goto cleanup" codepath can free it >> which is not very nice. >> >> Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx> > > Appears to be working ok now, thanks. Thanks. The sad part of the story was that this regression was introduced by a change to work around recent breakage observed when fetching from the http server github runs, and it was the primary purpose of pushing 1.6.4.3 out. Now we need to cut a 1.6.4.4 with this fix-on-fix soon, like tomorrow. > BTW: Is there any way to easily invoke GDB in case of such a problem > to get a real symbolic stack backtrace? > > I tried it on the 'git' binary, but of course this didn't work because > it invokes a git-pull script which again runs another git-remote-curl > binary. Not very easily. The best you can do is to run with GIT_TRACE to see what command actually dies and run that binary directly. gdb can choose to follow either parent or child across forks, but I do not know how to tell it to follow across execs into a different binary. -- 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