[bug #39851] Stack limit not restored for processes spawned through $(shell)

Follow-up Comment #3, bug #39851 (project make): OK, the test is racy. I see it was fixed in 3057357c from 10 Dec 2011. ___ Reply to this item at: ___

[bug #39851] Stack limit not restored for processes spawned through $(shell)

Follow-up Comment #2, bug #39851 (project make): Scratch that, that seems to be interaction between this and other downstream patches. The upstream test suite consistently passes. ___ Reply to this item at:

[bug #39851] Stack limit not restored for processes spawned through $(shell)

Follow-up Comment #1, bug #39851 (project make): Hmm, this breaks targets/SECONDARY. ___ Reply to this item at: ___ Message sent via/by Savannah http:

[bug #39825] bad redirection with >

Update of bug #39825 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Reply to this item at:

[bug #39825] bad redirection with >

Follow-up Comment #5, bug #39825 (project make): I can explain why sh.exe makes the difference. GNU Make on Windows always prefers a Unixy shell if it can find it. If it cannot find it, it uses cmd.exe. Also, Make does not invoke the shell if there are no shell features, such as quoting and red

[bug #39851] Stack limit not restored for processes spawned through $(shell)

URL: Summary: Stack limit not restored for processes spawned through $(shell) Project: make Submitted by: pmachata Submitted on: Чтв 22 Авг 2013 14:54:01 Severity: 3 - Normal

Re: [PATCH] Use spawn() in GNU Make on Cygwin, updated

> From: Pavel Fedin > Date: Thu, 22 Aug 2013 09:43:09 +0400 > Cc: bug-make@gnu.org > > What if we implement posix_spawn() for Cygwin ? Would you like > that ? If Paul accepts that for platforms other than Cygwin, I certainly won't mind. But please wait for Paul and Christopher to provide their

[bug #39825] bad redirection with >

Follow-up Comment #4, bug #39825 (project make): I found sh.exe and renamed it. Now objdump works properly. I can not however explain, why it works now. Thank you for help and sorry for bad identification, this bug seems to be really connected to sh.exe and not gmake itself.