From: Gene Pavlovsky <gene.pavlovsky@gmail.com>
To: cygwin@cygwin.com
Subject: Re: TortoiseGit + Cygwin git: unified diff fails (cygheap read copy failed)
Date: Sun, 20 Nov 2016 16:42:00 -0000 [thread overview]
Message-ID: <CAPTiy3PpJ=9e+4nDTTmwt_+NLYyW6gFPoxcLM_r1GbaScQWzTw@mail.gmail.com> (raw)
In-Reply-To: <CAPTiy3PrDfaOOsuefgAh6q-RiCsHVYoy9bgtqSzwv5QRmRhquw@mail.gmail.com>
On 17 November 2016 at 02:42, Gene Pavlovsky <gene.pavlovsky@gmail.com> wrote:
> Hey everybody!
>
> I'm using TortoiseGit with Cygwin git (Cygwin workarounds enabled in
> advanced TortoiseGit settings). For the most part, everything works
> correctly.
> The only problem: in TortoiseGit log for any repository, right-click
> any commit, pick "show changes as unified diff", there's an error
> dialog:
>
> ```
> Could not get unified diff.
> 1 [main] git 2292 child_copy: cygheap read copy failed,
> 0x180302408..0x18030F230, done 0, windows pid 2292, Win32 error 6
> 411 [main] git 2292 C:\cygwin\bin\git.exe: *** fatal error - ccalloc
> would have returned NULL
> ```
>
> Actually I've had this several months ago, just never got around to
> posting this to the list.
I've submitted an issue to the TortoiseGit issue tracker, the fix was
committed and it works now on my system.
https://gitlab.com/tortoisegit/tortoisegit/issues/2868
--Gene
--
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
prev parent reply other threads:[~2016-11-20 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 3:37 Gene Pavlovsky
2016-11-17 13:30 ` Csaba Raduly
2016-11-17 14:00 ` Gene Pavlovsky
2016-11-20 16:42 ` Gene Pavlovsky [this message]
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='CAPTiy3PpJ=9e+4nDTTmwt_+NLYyW6gFPoxcLM_r1GbaScQWzTw@mail.gmail.com' \
--to=gene.pavlovsky@gmail.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).