X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; q=dns; s=default; b=hoM
	TXAHLOPlv/DdctcFxgTmnGSABJmHMWZ3IT5uEcZbuwIEHcg8gLo1KPOnNGDh5Zol
	c+hL64BPxshkbyAedb1EfV8XZuttslbGvOkIugAx53JfbmHUGxT92LS99oL1EDsn
	PUXuYSvj5hyk1PPYJ6T083RCSZcXibY//eISF4NM=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; s=default; bh=Ykq7WKBUZ
	x7LbmTL6b/Nk20xlBs=; b=aKsprr3qcVZGvb9kVdSrTiNPm9VObAk1enQUaJrnT
	vwu6ry0fnmtQnSmUB8Tf44l3jNaLe0+lbx8gXjZ0LGJrSZiQvvdkzLQRl2hEuGZD
	n485+Qn5wfdAniat7ru8s40JgqOhR9Q5gXVEuCsDuwm0/H44UW3/t2Yy4cI9khQp
	3A=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: p3plsmtpa06-10.prod.phx3.secureserver.net
Message-ID: <52AB8D16.5080300@cesinst.com>
Date: Fri, 13 Dec 2013 14:41:26 -0800
From: Mark Stevans <retail5150@cesinst.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Desperate workaround for Git 64-Bit crashes
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Last Cygwin core update introduced disastrous (i.e. for me) Git bugs, 
where some commands instantly crash, e.g.:

     % git gc
     error: pack-refs died of signal 11
     error: failed to run pack-refs

Tried rebasing, reinstalling Git, no help.  Used "strace" to help 
identify executable "/usr/lib/git-core/git" as the problem: executing it 
in a shell with no arguments resulted in an immediate Segmentation 
Violation (executing "strace /usr/lib/git-core/git" worked fine). 
Surprisingly, "/bin/git" was a hard-link to the same file and started up 
fine (suggesting executable name/location dependencies).  In 
desperation, executed

     % cd /usr/lib/git-core
     % rm git
     % ln -s /bin/git

and, amazingly, "/usr/lib/git-core/git" now executes and high-level 
commands are working again.  Can't explain, but wanted to pass this 
strangeness on -- see log below....

MLS

[502 14:32:13][mstevans@Gragon: ~]$ cd /usr/lib/git-core
[503 14:32:21][mstevans@Gragon: /usr/lib/git-core]$ rm git
[504 14:32:22][mstevans@Gragon: /usr/lib/git-core]$ ln /bin/git .
[505 14:32:25][mstevans@Gragon: /usr/lib/git-core]$ cd
[507 14:32:31][mstevans@Gragon: ~]$ /usr/lib/git-core/git
Segmentation fault
[508 14:32:37][mstevans@Gragon: ~]$ cd /usr/lib/git-core
[510 14:32:47][mstevans@Gragon: /usr/lib/git-core]$ ./git
Segmentation fault
[511 14:32:52][mstevans@Gragon: /usr/lib/git-core]$ ln git dog
[512 14:33:02][mstevans@Gragon: /usr/lib/git-core]$ ./dog
Segmentation fault
[513 14:33:04][mstevans@Gragon: /usr/lib/git-core]$ rm dog
[514 14:33:09][mstevans@Gragon: /usr/lib/git-core]$ ln -s git dog
[515 14:33:13][mstevans@Gragon: /usr/lib/git-core]$ ./dog
Segmentation fault
[516 14:33:16][mstevans@Gragon: /usr/lib/git-core]$ rm dog
[517 14:33:22][mstevans@Gragon: /usr/lib/git-core]$ ln -s /bin/git dog
[518 14:33:25][mstevans@Gragon: /usr/lib/git-core]$ ./dog
usage: git [--version] [--exec-path[=<path>]] [--html-path] [--man-path] 
[--info-path]
            [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
            [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
            [-c name=value] [--help]
            <command> [<args>]

The most commonly used git commands are:
    add        Add file contents to the index
    bisect     Find by binary search the change that introduced a bug
    branch     List, create, or delete branches
    checkout   Checkout a branch or paths to the working tree
    clone      Clone a repository into a new directory
    commit     Record changes to the repository
    diff       Show changes between commits, commit and working tree, etc
    fetch      Download objects and refs from another repository
    grep       Print lines matching a pattern
    init       Create an empty git repository or reinitialize an 
existing one
    log        Show commit logs
    merge      Join two or more development histories together
    mv         Move or rename a file, a directory, or a symlink
    pull       Fetch from and merge with another repository or a local 
branch
    push       Update remote refs along with associated objects
    rebase     Forward-port local commits to the updated upstream head
    reset      Reset current HEAD to the specified state
    rm         Remove files from the working tree and from the index
    show       Show various types of objects
    status     Show the working tree status
    tag        Create, list, delete or verify a tag object signed with GPG

See 'git help <command>' for more information on a specific command.

[519 14:33:28][mstevans@Gragon: /usr/lib/git-core]$ rm git dog
[520 14:33:38][mstevans@Gragon: /usr/lib/git-core]$ ln -s /bin/git
[521 14:33:51][mstevans@Gragon: /usr/lib/git-core]$ ./git
usage: git [--version] [--exec-path[=<path>]] [--html-path] [--man-path] 
[--info-path]
            [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
            [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
            [-c name=value] [--help]
            <command> [<args>]

The most commonly used git commands are:
    add        Add file contents to the index
    bisect     Find by binary search the change that introduced a bug
    branch     List, create, or delete branches
    checkout   Checkout a branch or paths to the working tree
    clone      Clone a repository into a new directory
    commit     Record changes to the repository
    diff       Show changes between commits, commit and working tree, etc
    fetch      Download objects and refs from another repository
    grep       Print lines matching a pattern
    init       Create an empty git repository or reinitialize an 
existing one
    log        Show commit logs
    merge      Join two or more development histories together
    mv         Move or rename a file, a directory, or a symlink
    pull       Fetch from and merge with another repository or a local 
branch
    push       Update remote refs along with associated objects
    rebase     Forward-port local commits to the updated upstream head
    reset      Reset current HEAD to the specified state
    rm         Remove files from the working tree and from the index
    show       Show various types of objects
    status     Show the working tree status
    tag        Create, list, delete or verify a tag object signed with GPG

See 'git help <command>' for more information on a specific command.

[522 14:33:52][mstevans@Gragon: /usr/lib/git-core]$


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

