# segfault during clone via http 5 messages from 2009-02-04 to 2009-02-04. Participants: Adam Thorsen, Jay Soffian, Johannes Schindelin, Mike Hommey. Thread: https://gitlist.dev/t/17561 ## Adam Thorsen, 2009-02-04 16:10 Subject: segfault during clone via http Message-ID: URL: https://gitlist.dev/e/loom.20090204T160827-822%40post.gmane.org ``` Git is segfaulting when downloading from a repo via http. Here's what the output looks like: http://gist.github.com/58167. Anybody seen this before or know how I can debug it? I've made sure my git (1.6.1) is compiled with libcurl. ``` ## Jay Soffian, 2009-02-04 18:00 Subject: Re: segfault during clone via http Message-ID: <76718490902041000x3cda2390t25254e8372c9af50@mail.gmail.com> URL: https://gitlist.dev/e/76718490902041000x3cda2390t25254e8372c9af50%40mail.gmail.com In-Reply-To: ``` On Wed, Feb 4, 2009 at 11:10 AM, Adam Thorsen wrote: > Git is segfaulting when downloading from a repo via http. Here's what the > output looks like: http://gist.github.com/58167. Anybody seen this before or > know how I can debug it? I've made sure my git (1.6.1) is compiled with libcurl. Please run git under gdb so that there is a stacktrace to work from. Here is an example of running git under gdb and providing a trace: http://article.gmane.org/gmane.comp.version-control.git/107860 j. ``` ## Adam Thorsen, 2009-02-04 18:35 Subject: Re: segfault during clone via http Message-ID: URL: https://gitlist.dev/e/loom.20090204T183407-350%40post.gmane.org In-Reply-To: <76718490902041000x3cda2390t25254e8372c9af50@mail.gmail.com> ``` Here is the stack trace: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x00494000 0x0015bb04 in multi_runsingle () (gdb) bt #0 0x0015bb04 in multi_runsingle () #1 0x0015d5af in curl_multi_perform () #2 0x000b8782 in step_active_slots () at http.c:450 #3 0x000b881c in run_active_slot (slot=0x50a450) at http.c:474 #4 0x000bac5c in fetch (walker=0x5008d0, sha1=0x4a791c "?u^?9l?\003?5??#??X\"?XL") at http-walker.c:846 ``` ## Johannes Schindelin, 2009-02-04 20:34 Subject: Re: segfault during clone via http Message-ID: URL: https://gitlist.dev/e/alpine.DEB.1.00.0902042132110.10279%40pacific.mpi-cbg.de In-Reply-To: ``` Hi, On Wed, 4 Feb 2009, Adam Thorsen wrote: > > Here is the stack trace: > > Program received signal EXC_BAD_ACCESS, Could not access memory. > Reason: KERN_INVALID_ADDRESS at address: 0x00494000 > 0x0015bb04 in multi_runsingle () > (gdb) bt > #0 0x0015bb04 in multi_runsingle () > #1 0x0015d5af in curl_multi_perform () > #2 0x000b8782 in step_active_slots () at http.c:450 > #3 0x000b881c in run_active_slot (slot=0x50a450) at http.c:474 > #4 0x000bac5c in fetch (walker=0x5008d0, > sha1=0x4a791c "?u^?9l?\003?5??#??X\"?XL") at http-walker.c:846 FWIW I think the issue is related to the double cleanup I mentioned to Mike Hommey earlier. At least when I undo the double cleanup, I do not get any segfaults anymore. Ciao, Dscho ``` ## Mike Hommey, 2009-02-04 21:39 Subject: Re: segfault during clone via http Message-ID: <20090204213913.GA7806@glandium.org> URL: https://gitlist.dev/e/20090204213913.GA7806%40glandium.org In-Reply-To: ``` On Wed, Feb 04, 2009 at 09:34:36PM +0100, Johannes Schindelin wrote: > Hi, > > On Wed, 4 Feb 2009, Adam Thorsen wrote: > > > > > Here is the stack trace: > > > > Program received signal EXC_BAD_ACCESS, Could not access memory. > > Reason: KERN_INVALID_ADDRESS at address: 0x00494000 > > 0x0015bb04 in multi_runsingle () > > (gdb) bt > > #0 0x0015bb04 in multi_runsingle () > > #1 0x0015d5af in curl_multi_perform () > > #2 0x000b8782 in step_active_slots () at http.c:450 > > #3 0x000b881c in run_active_slot (slot=0x50a450) at http.c:474 > > #4 0x000bac5c in fetch (walker=0x5008d0, > > sha1=0x4a791c "?u^?9l?\003?5??#??X\"?XL") at http-walker.c:846 > > FWIW I think the issue is related to the double cleanup I mentioned to > Mike Hommey earlier. At least when I undo the double cleanup, I do not > get any segfaults anymore. I thought it was not applied, in the end ? Mike ```