{"thread":{"id":"17561","subject":"segfault during clone via http","startedAt":"2009-02-04T16:10:00Z","lastAt":"2009-02-04T21:39:13Z","messageCount":5,"participants":["Adam Thorsen","Jay Soffian","Johannes Schindelin","Mike Hommey"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"103161","messageId":"loom.20090204T160827-822@post.gmane.org","threadId":"17561","inReplyTo":null,"subject":"segfault during clone via http","fromName":"Adam Thorsen","fromEmail":"adam.thorsen@gmail.com","sentAt":"2009-02-04T16:10:00Z","receivedAt":"2009-02-04T16:10:00Z","isPatch":false,"sender":{"key":"adam.thorsen@gmail.com","avatar":null},"body":"Git is segfaulting when downloading from a repo via http. Here's what the\noutput looks like: http://gist.github.com/58167. Anybody seen this before or\nknow how I can debug it? I've made sure my git (1.6.1) is compiled with libcurl.\n"},{"id":"103174","messageId":"76718490902041000x3cda2390t25254e8372c9af50@mail.gmail.com","threadId":"17561","inReplyTo":"loom.20090204T160827-822@post.gmane.org","subject":"Re: segfault during clone via http","fromName":"Jay Soffian","fromEmail":"jaysoffian@gmail.com","sentAt":"2009-02-04T18:00:28Z","receivedAt":"2009-02-04T18:00:28Z","isPatch":false,"sender":{"key":"jaysoffian@gmail.com","avatar":"https://avatars.githubusercontent.com/u/155970?v=4"},"body":"On Wed, Feb 4, 2009 at 11:10 AM, Adam Thorsen wrote:\n> Git is segfaulting when downloading from a repo via http. Here's what the\n> output looks like: http://gist.github.com/58167. Anybody seen this before or\n> know how I can debug it? I've made sure my git (1.6.1) is compiled with libcurl.\n\nPlease run git under gdb so that there is a stacktrace to work from. Here is an\nexample of running git under gdb and providing a trace:\n\nhttp://article.gmane.org/gmane.comp.version-control.git/107860\n\nj.\n"},{"id":"103178","messageId":"loom.20090204T183407-350@post.gmane.org","threadId":"17561","inReplyTo":"76718490902041000x3cda2390t25254e8372c9af50@mail.gmail.com","subject":"Re: segfault during clone via http","fromName":"Adam Thorsen","fromEmail":"adam.thorsen@gmail.com","sentAt":"2009-02-04T18:35:39Z","receivedAt":"2009-02-04T18:35:39Z","isPatch":false,"sender":{"key":"adam.thorsen@gmail.com","avatar":null},"body":"\nHere is the stack trace:\n\nProgram received signal EXC_BAD_ACCESS, Could not access memory.\nReason: KERN_INVALID_ADDRESS at address: 0x00494000\n0x0015bb04 in multi_runsingle ()\n(gdb) bt\n#0 0x0015bb04 in multi_runsingle ()\n#1 0x0015d5af in curl_multi_perform ()\n#2 0x000b8782 in step_active_slots () at http.c:450\n#3 0x000b881c in run_active_slot (slot=0x50a450) at http.c:474\n#4 0x000bac5c in fetch (walker=0x5008d0, \nsha1=0x4a791c \"?u^?9l?\\003?5??#??X\\\"?XL\") at http-walker.c:846\n"},{"id":"103198","messageId":"alpine.DEB.1.00.0902042132110.10279@pacific.mpi-cbg.de","threadId":"17561","inReplyTo":"loom.20090204T183407-350@post.gmane.org","subject":"Re: segfault during clone via http","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2009-02-04T20:34:36Z","receivedAt":"2009-02-04T20:34:36Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Wed, 4 Feb 2009, Adam Thorsen wrote:\n\n> \n> Here is the stack trace:\n> \n> Program received signal EXC_BAD_ACCESS, Could not access memory.\n> Reason: KERN_INVALID_ADDRESS at address: 0x00494000\n> 0x0015bb04 in multi_runsingle ()\n> (gdb) bt\n> #0 0x0015bb04 in multi_runsingle ()\n> #1 0x0015d5af in curl_multi_perform ()\n> #2 0x000b8782 in step_active_slots () at http.c:450\n> #3 0x000b881c in run_active_slot (slot=0x50a450) at http.c:474\n> #4 0x000bac5c in fetch (walker=0x5008d0, \n> sha1=0x4a791c \"?u^?9l?\\003?5??#??X\\\"?XL\") at http-walker.c:846\n\nFWIW I think the issue is related to the double cleanup I mentioned to \nMike Hommey earlier. At least when I undo the double cleanup, I do not \nget any segfaults anymore.\n\nCiao,\nDscho\n"},{"id":"103211","messageId":"20090204213913.GA7806@glandium.org","threadId":"17561","inReplyTo":"alpine.DEB.1.00.0902042132110.10279@pacific.mpi-cbg.de","subject":"Re: segfault during clone via http","fromName":"Mike Hommey","fromEmail":"mh@glandium.org","sentAt":"2009-02-04T21:39:13Z","receivedAt":"2009-02-04T21:39:13Z","isPatch":false,"sender":{"key":"mh@glandium.org","avatar":"https://avatars.githubusercontent.com/u/1038527?v=4"},"body":"On Wed, Feb 04, 2009 at 09:34:36PM +0100, Johannes Schindelin wrote:\n> Hi,\n> \n> On Wed, 4 Feb 2009, Adam Thorsen wrote:\n> \n> > \n> > Here is the stack trace:\n> > \n> > Program received signal EXC_BAD_ACCESS, Could not access memory.\n> > Reason: KERN_INVALID_ADDRESS at address: 0x00494000\n> > 0x0015bb04 in multi_runsingle ()\n> > (gdb) bt\n> > #0 0x0015bb04 in multi_runsingle ()\n> > #1 0x0015d5af in curl_multi_perform ()\n> > #2 0x000b8782 in step_active_slots () at http.c:450\n> > #3 0x000b881c in run_active_slot (slot=0x50a450) at http.c:474\n> > #4 0x000bac5c in fetch (walker=0x5008d0, \n> > sha1=0x4a791c \"?u^?9l?\\003?5??#??X\\\"?XL\") at http-walker.c:846\n> \n> FWIW I think the issue is related to the double cleanup I mentioned to \n> Mike Hommey earlier. At least when I undo the double cleanup, I do not \n> get any segfaults anymore.\n\nI thought it was not applied, in the end ?\n\nMike\n"}]}