All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Bena <benapetr@gmail.com>
To: Thomas Braun <thomas.braun@virtuell-zuhause.de>
Cc: git@vger.kernel.org, msysGit <msysgit@googlegroups.com>
Subject: Re: BUG I can't start git on Windows 7
Date: Mon, 8 Sep 2014 15:23:26 +0200	[thread overview]
Message-ID: <CA+4EQ5e4==-eZDw7y4yj-vQS1dZsQig3xZc7eTkoCWF=SxU9cg@mail.gmail.com> (raw)
In-Reply-To: <540DAD4B.9000208@virtuell-zuhause.de>

Hi,

Windows 7 enterprise (Windows [Version 6.1.7601])

I mention it because IMHO windows git is based on cygwin and because I
can see cygwin mentioned in error message. I didn't install it by
hand, I think it was part of git installation package.

On Mon, Sep 8, 2014 at 3:21 PM, Thomas Braun
<thomas.braun@virtuell-zuhause.de> wrote:
> Am 08.09.2014 um 11:15 schrieb Petr Bena:
>> I installed git on my system using official package from git-scm.com
>> but I can't launch it, I am always getting this error:
>>
>> C:\Users\petr.bena>"C:\Program Files (x86)\Git\bin\sh.exe" --login -i
>>       0 [main] us 0 init_cheap: VirtualAlloc pointer is null, Win32 error 487
>> AllocationBase 0x0, BaseAddress 0x68570000, RegionSize 0x40000, State 0x10000
>> C:\Program Files (x86)\Git\bin\sh.exe: *** Couldn't reserve space for
>> cygwin's heap, Win32 error 0
>>
>>
>> At some point this could be an issue with cygwin, but I am not sure.
>> Did anyone had similar issue?
>
> [CC'ing msysgit]
>
> Do you have cygwin installed, or why do you mention cygwin?
> What windows are you running?
>
>

  reply	other threads:[~2014-09-08 13:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08  9:15 BUG I can't start git on Windows 7 Petr Bena
2014-09-08 13:21 ` Thomas Braun
2014-09-08 13:23   ` Petr Bena [this message]
2014-09-08 15:34 ` Konstantin Khomoutov
2014-09-08 15:56   ` Petr Bena
2014-09-08 15:57     ` Petr Bena
2014-09-08 16:02   ` Thomas Braun

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='CA+4EQ5e4==-eZDw7y4yj-vQS1dZsQig3xZc7eTkoCWF=SxU9cg@mail.gmail.com' \
    --to=benapetr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=msysgit@googlegroups.com \
    --cc=thomas.braun@virtuell-zuhause.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.