This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: mem allocation / heap_chunk

On Thu, 27 Feb 2003, Fabrice Marchal wrote:

> Hi,
> I have come accross the 384 Mb limit for allocating memory in cygwin.
> (e.g.  char* pnt = new char[ long size = 500*1024*1024 ]; will not work )
> I have been able to modify this using the workaround documented in the
> Users Guide (
> I would like to know if there is a way to do the same within code so
> that end-users
> who receive a cygwin-compiled code do not require to go into the hassle of
> using regtool or regedit
> Is that feasible?
> Thanks
> fm

Sure.  Write a script that uses regtool.  Make it a postinstall script,
put a "Reboot or restart Cygwin" in the README.  It would be more robust
if you also check the heap_chunk value before writing to it, in case the
user already has it set to something higher.
      |\      _,,,---,,_		pechtcha at cs dot nyu dot edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor at watson dot ibm dot com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]