Home/ Questions/Q 9266539
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-18T14:20:33+00:00

I have installed github version 0.8.4, but when i try to fetch something from

  • 0

I have installed github version 0.8.4,
but when i try to fetch something from git, it is showing this message.

Fetching all tracking branches from Queue-iOS completed successfully.

command: git fetch Queue-iOS

error: git-credential-osxkeychain died of signal 11
error: git-credential-osxkeychain died of signal 11
error: git-credential-osxkeychain died of signal 11
error: git-credential-osxkeychain died of signal 11
From https://github.com/appstute/Queue-iOS
   59bb075..b2da838  master     -> Queue-iOS/master

It is a problem regarding keychain,
when i go for pull from git hub, the following message is displayed

Pulling all tracking branches from Queue-iOS encountered an error.

command: git pull Queue-iOS

error: git-credential-osxkeychain died of signal 11
error: git-credential-osxkeychain died of signal 11
error: git-credential-osxkeychain died of signal 11
error: git-credential-osxkeychain died of signal 11
You asked to pull from the remote 'Queue-iOS', but did not specify
a branch. Because this is not the default configured remote
for your current branch, you must specify a branch on the command line.

error = 1

Here Queue-iOS is the local folder I have configured on git. Please help.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I am using Mac OS X 10.7.5. I recently downloaded git 1.8.1.2 for Mac. Having it installed, I bumped into the same signal 11 error message when running:

    $git credential-osxkeychain

    which in turn runs:

    /usr/local/git/bin/git-credential-osxkeychain

    Signal 11 is SEGFAULT which might indicate a bug (e.g. dereferencing a null pointer) with the git-credential-osxkeychain program.

    I followed instructions on caching your github password and grabbed a new copy of git-credential-osxkeychain from S3. That resolved the problem. The new copy is of different size which makes me guess the bug has been patched.

    In the meantime, I believe using a URL like git@github.com:yang3wei/octopress-3-in-one in the config should also work around the problem as it bypasses HTTPS and uses SSH instead where the key chain helper is not invoked any more.

    • 0