From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: "cant commit memory for stack" error with perl
Date: Mon, 02 Apr 2012 14:45:00 -0000 [thread overview]
Message-ID: <20120402144510.GE9924@calimero.vinschen.de> (raw)
In-Reply-To: <4F79B7EF.7050108@peralex.com>
On Apr 2 16:30, Noel Grandin wrote:
>
>
> On 2012-04-02 12:19, Corinna Vinschen wrote:
> >Just download cygwin1-20120401.dll.bz2, bunzip it, chmod +x it,
> >and then replace cygwin1.dll in /bin with that file from Windows
> >Explorer. That's it
>
> Thanks for that suggestion.
> Tried it. Also tried rebooting.
> Also tried disabling DEP and ASLR.
> Still no joy.
> Sigh...
If you can strip your perl script to the bare minimum necessary to
reproduce the issue, I can take a look if I can reproduce it.
Oh, and, where is your perl.exe based to? In other words, what does
$ objdump -h /bin/perl.exe | grep '\.text'
print? (objdump is part of the binutils package).
If it's *not*
00401000
but rather something like
55691000
call `rebase -b 0x400000 /bin/perl.exe'
and try again.
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
next prev parent reply other threads:[~2012-04-02 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 12:12 Noel Grandin
2012-04-01 18:01 ` Larry Hall (Cygwin)
2012-04-02 7:53 ` Corinna Vinschen
2012-04-02 8:23 ` Noel Grandin
2012-04-02 8:58 ` Corinna Vinschen
2012-04-02 9:49 ` Noel Grandin
2012-04-02 10:20 ` Corinna Vinschen
2012-04-02 14:30 ` Noel Grandin
2012-04-02 14:45 ` Corinna Vinschen [this message]
2012-04-02 14:55 ` Noel Grandin
2012-04-03 6:58 ` Noel Grandin
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=20120402144510.GE9924@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).