Re: fork: can't reserve memory for parent stack

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Aug  8 12:11, Marco Atzeri wrote:
> 
> 
> On 05/08/2015 09:56, Corinna Vinschen wrote:
> >On Aug  3 23:37, Marco Atzeri wrote:
> >>Testing on 64bit latest pure-ftp, I hit this issue:
> >>
> >>/usr/sbin/pure-ftpd.exe -d
> >>       1 [main] pure-ftpd 8860 E:\cygwin64\usr\sbin\pure-ftpd.exe: *** fatal
> >>error in forked process - fork: can't reserve memory for parent stack
> >>0x1E0000 - 0x3E0000, (child has 0x210000 - 0x410000), Win32 error 487
> >>    1593 [main] pure-ftpd 8860 cygwin_exception::open_stackdumpfile: Dumping
> >>stack trace to pure-ftpd.exe.stackdump
> >>       2 [main] pure-ftpd 8832 fork: child -1 - forked process 8860 died
> >>unexpectedly, retry 0, exit code 0x100, errno 11
> >>
> >>
> >>pure-ftpd.exe.stackdump is empty, and the code run fine on 32bit
> >>version.
> >>
> >>attached the process memory map.
> >>
> >>Suggestion ?
> >
> >Hmm, sorry, no.  Where is the unusual stack layout coming from?!?
> >
> >
> >Corinna
> >
> 
> No idea, but it seems common on my machine
> see three maps on different programs.
> All have stack and heap intermixed.

The first (bash) and the third (mintty) one look normal w/ stack at
0x30000 - 0x230000.  The second one (pure-ftpd) has an uncomment main
stack area at 0x1A0000 - 0x3a0000 and the area is apparently taken
by something else when forking.
It's totally unclear to me why the executable main thread doesn't get
the standard stack area, and what it's taken by what.  That's info
you can't get from the maps, unfortunately.

> What is the meaning of tid ?

Thread ID, just like the PID for processes.


Corinna

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

Attachment: pgpUrza3AjCse.pgp
Description: PGP signature