On Sun, Jan 16, 2011 at 04:32:17PM +0200, Paavo Leinonen wrote:
>Hi,
>
>I have read [1] and set heap_chunk_in_mb to 2048, but
>max_memory.exe gives me only 1920 MB. I need (almost)
>2048 MB to be able to manipulate BIG (map) images, how
>can get 2048 megabytes available for my program?
>
>Where has
On Thu, Dec 30, 2010 at 9:01 AM, Eric Blake (cygwin) wrote:
> A new release of bash, 4.1.9-1, has been uploaded for testing and will
> soon reach a mirror near you. Bash 3.2.51-24 remains current until I am
> sure this doesn't introduce any major regressions.
This version of bash works great for
Pierce Morton wrote:
> I've recently installed cygwin using the web installer, and have found
> an error in the way that cygpath translates junction point paths from
> *nix to Windows paths when dealing with a junction point.
The issue is that Cygwin treats reparse points as symlinks. IMO, the
mo
Corinna Vinschen wrote:
> > This leaves cygpath completely unable to translate the original path
> > of an NTFS junction. This is proving to be a problem for me (I'm
> > trying to use the output of cygpath for the equivalent of a backtick
> > operation in another script...)
>
> Sorry if I don't
Hi,
I have read [1] and set heap_chunk_in_mb to 2048, but
max_memory.exe gives me only 1920 MB. I need (almost)
2048 MB to be able to manipulate BIG (map) images, how
can get 2048 megabytes available for my program?
Where has the 128 MB (2048 - 1920) gone? I also tried
increasing heap_chunk_in_mb
5 matches
Mail list logo
