public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: enabling /largeaddressaware for cygwin in windows 7 64-bit
Date: Thu, 04 Aug 2011 15:54:00 -0000	[thread overview]
Message-ID: <20110804155355.GE21692@calimero.vinschen.de> (raw)
In-Reply-To: <8C8430B888BACD4E91AC1CBE7000204F1D74558C@FISHERCAT.middlebury.edu>

On Aug  4 15:19, Amidon, William H. wrote:
> Hello,
> 
> I am not a programming expert, and i wonder if you could give me some
> basic advice.
> 
> I am running cygwin on a 64-bit Dell XPS, running Windows 7, with a
> Core i5 processor, and 12 GB of RAM installed.
> 
> The fortran 90 code I am running keeps running out of memory (virtual
> memory or stack overflow errors) on jobs that the computer should

The main thread has a 2 Megs stack by default (Windows default).
If you're running out of stack space, there's not much we can do.
There's some way to define the default stacksize in the executable
header but off the top of my head I don't know how to change it.

> easily handle.  I have increased the paging memory to 36 MB, but I am
> afraid that CygWin is still being limited to ~ 1 GB of memory.

It's not.  It's limited to 2 Gigs usually, being a 32 bit DLL.  Only by
setting the large address awareness flag in the executable (not the
DLL!) you get a max of 4 Gigs of memory on 64 bit Windows.

> My problem is very similar to what is described here:
> http://cygwin.com/ml/cygwin/2011-01/msg00196.html
> 
> I followed the instructions at [1] and [2] to increase the heap chunk

[2]?  That's not for 64 bit Windows.  If you tried that, take it back.

> available to cygwin, but I have also read that adding a
> /largeaddressaware link might further increase the amount of memory
> available to cygwin (see [3], which confused me a lot). 

If that confused you, you should probably not tamper with these
settings.  The maximum you should try is this:

- Revert the settings from [1].
- Download the latest Cygwin developer snapshot (only the DLL) from
  http://cygwin.com/snapshots.
- peflags --bigaddr=1 your_executable.exe

If that doesn't help, you're out of luck.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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

  reply	other threads:[~2011-08-04 15:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04 15:20 Amidon, William H.
2011-08-04 15:54 ` Corinna Vinschen [this message]
2011-08-04 17:37   ` Charles Wilson
2011-08-04 18:17     ` Corinna Vinschen
2011-08-04 22:17       ` Charles Wilson
2011-08-05  6:33         ` Corinna Vinschen

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=20110804155355.GE21692@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).