> On Feb 24, 2015, at 4:03 PM, Dan Langille (dalangil) <[email protected]>
> wrote:
>
>> On Feb 19, 2015, at 3:35 PM, brian m. carlson <[email protected]>
>> wrote:
>>
>> On Wed, Feb 18, 2015 at 04:17:46PM +0000, Dan Langille (dalangil) wrote:
>>> I just built from ‘master’, on FreeBSD 9.3:
>>>
>>> cd ~/src
>>> git clone https://github.com/git/git.git
>>> cd git
>>> gmake
>>>
>>> Then tried ~/src/git/git clone https://OUR_REPO
>>>
>>> It cores too, and I see: git-remote-https.core
>>
>> Can you compile with debugging symbols and provide a backtrace? I'm not
>> seeing any such behavior on my end, and I'm not sure whether it's my
>> patch or something else that might be present in master.
>
> The problem originally occurred under VMware Fusion and I’m unable to get a
> backtrace from it.
> I suspect memory constraints are a factor. There’s only 5GB RAM available to
> this VM.
>
> I have tried in another VM and that succeeds. All good there. It has 40GB
> RAM.
>
> I am going to try this on a third system. At present, we’re just 50/50 on
> success.
We have made progress I think.
With stock git:
tl;dr: 1 - with a ticket, you get prompted, but hitting ENTER succeeds.
2 - without a ticket, nothing works
With patched git:
tl;dr: 1 - with a ticket, entering credentials, SUCCEEDS; just hit enter,
failure
2 - without a ticket, entering credentials, SUCCEEDS
Here is my test, with a valid kerberos ticket:
$ git clone https://git.example.com/git/clamav-bytecode-compiler
Cloning into 'clamav-bytecode-compiler'...
Username for 'https://git.example.com':
Password for 'https://git.example.com':
^Cmote: Counting objects: 224546
$
