# Fwd: segmentation fault 11 2 messages from 2015-02-08 to 2015-02-09. Participants: David Krmpotic, Jeff King. Thread: https://gitlist.dev/t/38530 ## David Krmpotic, 2015-02-08 17:56 Subject: Fwd: segmentation fault 11 Message-ID: URL: https://gitlist.dev/e/CAOFaZ%2B42Wbk8t_UmLGwxhRo%2BZZOhpUT32o5wuj%2BLcJhaELOu5A%40mail.gmail.com In-Reply-To: ``` I updated to 2.3.0 on my OSX 10.9.5 and when trying to push to github (git push -u origin master), I get: Segmentation fault: 11 Switched back to 1.8.5.5 and it works... Report: http://cl.ly/1u3E412N0D2Z Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 VM Regions Near 0: --> __TEXT 0000000102b1c000-0000000102c78000 [ 1392K] r-x/rwx SM=COW /usr/local/Cellar/git/2.3.0/bin/git Thread 0 Crashed:: Dispatch queue: com.apple.main-thread ``` ## Jeff King, 2015-02-09 01:36 Subject: Re: Fwd: segmentation fault 11 Message-ID: <20150209013657.GC21072@peff.net> URL: https://gitlist.dev/e/20150209013657.GC21072%40peff.net In-Reply-To: ``` On Sun, Feb 08, 2015 at 06:56:14PM +0100, David Krmpotic wrote: > I updated to 2.3.0 on my OSX 10.9.5 and when trying to push to github > (git push -u origin master), I get: > > Segmentation fault: 11 > > Switched back to 1.8.5.5 and it works... Is this reproducible easily? If so, can you do one or both of: 1. Get a backtrace by running git-push under gdb (and/or loading gdb on the core file if you have it). The report you linked mentions that we were in "0x0000000102b70ebe cmd_push + 2466", but without having your binary, that only gives a vague sense of the line that caused the problem. 2. Bisect the bug between v1.8.5.5 and v2.3.0. I can walk you through the specific steps if you've never bisected before. Thanks. -Peff ```