From: "Stephen M. McQuay" <stephen@mcquay.me>
To: git@vger.kernel.org
Subject: Segmentation fault on clone
Date: Fri, 19 Jan 2018 10:08:57 -0800 [thread overview]
Message-ID: <20180119180855.GA98561@smm.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
I submitted a bug against the brew project when git version 2.16.0
started segfaulting:
https://github.com/Homebrew/homebrew-core/issues/23045#issuecomment-358891009
I've built git from master from https://github.com/git/git and was able
to reproduce (no surprise, the top commit claims it's 2.16.0), and also
built from the `next` branch which yields similar results.
I'm on latest customer release of MacOS:
$ uname -a
Darwin smm.local 17.3.0 Darwin Kernel Version 17.3.0: Thu Nov 9 18:09:22 PST 2017; root:xnu-4570.31.3~1/RELEASE_X86_64 x86_64
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.13.2
BuildVersion: 17C205
The clone url in question: git@github.com:gdamore/tcell.git
Any other information that would be helpful?
Respectfully,
--
Stephen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-01-19 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 18:08 Stephen M. McQuay [this message]
2018-01-19 18:22 ` Segmentation fault on clone Todd Zullinger
2018-01-19 18:26 ` Stephen M. McQuay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180119180855.GA98561@smm.local \
--to=stephen@mcquay.me \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).