threads / discuss / 38530

Fwd: segmentation fault 11

Subject: Fwd: segmentation fault 11

## tl;dr

2 messages between Feb 8, 2015 and Feb 9, 2015.

replies: 1people: 2as markdown or json

David Krmpotic· Feb 8, 2015, 17:56 UTC · lore

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· Feb 9, 2015, 01:36 UTC · re: David Krmpotic · lore

Re: Fwd: segmentation fault 11

On Sun, Feb 08, 2015 at 06:56:14PM +0100, David Krmpotic wrote:
Show 6 quoted lines
> 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

← back to recent threads