miawendell / puttycyg

Automatically exported from code.google.com/p/puttycyg
0 stars 2 forks source link

Clean Installation of Cygin 1.7.5-1; Unpackage and run puttycyg with "putty.exe -cygterm -"; result PuTTY Fatal Error, Failed to allocate pseudoterminal #40

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Please read the FAQ and check existing issues before creating a new issue.

What steps will reproduce the problem?
1. Install Cygwin 1.7.5
2. Install PuTTYCyg
3. Run "putty.exe -cygterm -"

What is the expected result?  What happens instead?

I would expect putty to connect to a cygwin shell, but instead it produces 
"PuTTY Fatal Error, Failed to allocate pseudoterminal"

PutTTYcyg version: 20091228
Cygwin version: 1.7.5
Windows version: XP Pro SP2

If you are experiencing performance issues, do you have a multi-core system
or multiple CPUs?

Do you have any firewall software installed?
Nope

Please attach your PuTTY configuration.  Use this Windows command to create
putty.reg:
REG EXPORT HKEY_CURRENT_USER\Software\SimonTatham\PuTTY putty.reg

Please provide any additional information below.

Previously had a working puttycyg with cygwin 1.5 but ceased to work after
clean install to 1.7.5. Before upgrade, the entire previous cygwin
installation directory was deleted, as well as all associated registry
keys. There are not multiple copies of the cygwin1.dll on the system path,
only in $CYGWIN_HOME/bin.

I have run mkpasswd and mkgroup after my initial cygwin install. My home is
set to /home/$WINDOWS_USERNAME under the cygwin install.

Installation seems to be detected ok, as if I remove cygwin1.dll from /bin,
puttycyg complains that it is missing when attempting to start session.
Putting it back ceases that errorm, but results in the "failed to allocate
pseudoterminal" error.

Googling for the error only seems to return the piece source good where the
error string is set. I can't believe I'm the only one on earth to have had
this problem if a configuration issue.

Original issue reported on code.google.com by JCerwin...@gmail.com on 10 May 2010 at 10:11

Attachments:

GoogleCodeExporter commented 8 years ago
Scratch this report. I'm clearly having a problem with the cygwin install scrips
instead of puttycyg.

2010/05/11 10:18:25 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/000-cygwin-post-install.sh
      9 [main] bash 3744 C:\cygwin\bin\bash.exe: *** fatal error - couldn't allocate
heap, Win32 error 487, base 0x6D0000, top 0x730000, reserve_size 389120, 
allocsize
393216, page_const 4096
      8 [main] bash 2840 fork: child -1 - died waiting for longjmp before
initialization, retry 0, exit code 0x100, errno 11
      9 [main] bash 3936 C:\cygwin\bin\bash.exe: *** fatal error - couldn't allocate
heap, Win32 error 487, base 0x6D0000, top 0x730000, reserve_size 389120, 
allocsize
393216, page_const 4096
4142302 [main] bash 2840 fork: child -1 - died waiting for longjmp before
initialization, retry 0, exit code 0x100, errno 11
      9 [main] bash 2100 C:\cygwin\bin\bash.exe: *** fatal error - couldn't allocate
heap, Win32 error 487, base 0x6D0000, top 0x730000, reserve_size 389120, 
allocsize
393216, page_const 4096
9140588 [main] bash 2840 fork: child -1 - died waiting for longjmp before
initialization, retry 0, exit code 0x100, errno 11
      9 [main] bash 3940 C:\cygwin\bin\bash.exe: *** fatal error - couldn't allocate
heap, Win32 error 487, base 0x6D0000, top 0x730000, reserve_size 389120, 
allocsize
393216, page_const 4096
16307872 [main] bash 2840 fork: child -1 - died waiting for longjmp before
initialization, retry 0, exit code 0x100, errno 11
      9 [main] bash 3588 C:\cygwin\bin\bash.exe: *** fatal error - couldn't allocate
heap, Win32 error 487, base 0x6D0000, top 0x730000, reserve_size 389120, 
allocsize
393216, page_const 4096
27325926 [main] bash 2840 fork: child -1 - died waiting for longjmp before
initialization, retry 0, exit code 0x100, errno 11
/etc/postinstall/000-cygwin-post-install.sh: fork: Resource temporarily 
unavailable
2010/05/11 10:18:57 abnormal exit: exit code=128

Original comment by JCerwin...@gmail.com on 11 May 2010 at 2:44

GoogleCodeExporter commented 8 years ago
I'm receiving the same error message as above "Failed to allocate 
pseudoterminal". 
Under medgar123's comment he posted some information which nulls the request,
unfortunately I don't know what he ran to get that data so I can determine 
whether is
issue with my install or the puttycyg.

Cheers

Original comment by helmu...@gmail.com on 21 May 2010 at 3:22

GoogleCodeExporter commented 8 years ago
I was pulling my hair out for a while trying to figure it what my problem was, 
and
eventually stumbled upon the solution that fixed my Ills. I don't know if this 
will
help you, but I found that our Dell boxes come preinstalled with some Wave 
Systems
Corp TPM garbage, which was interfering with my installation of Cygwin 1.7.5. I 
don't
even know who finds that trash useful, much less anything than utterly annoying 
and
interfering with the operation of a clean system...

Check item 44. http://www.cygwin.com/faq/faq.using.html

After removing it, I cleaned out my borked install directory and tried again 
and it
worked. 

What happens right after the cygwin install? When I was doing it while this TPM 
was
active, I could run the batch file and launch cygwin, but I wouldn't have a home
directory, /bin wouldn't be on the path, etc. I was able originally to create a
.bashrc and I created my home directory manually, so I didn't think anything was
really wrong at first. I thought it was due to coming from 1.5 or something and 
I
just had to tweak it manually as a result. But then puttycyg would never 
connect.

After finally discovering that I might be prevented from install by some TPM, I
removed it, reinstalled, and ran the batch file. Everything was working, I had a
$HOME, commands were on the path, etc. I didn't have to do any of this manual
configuring. Then I launched puttycyg and it worked immediately, no hassle.

Be sure to check your /var/log directory and check the setup log after setup
completes. I would have saved a lot of time if I had immediately been searching 
on
the error: "couldn't allocate
heap, Win32 error 487, base 0x6D0000, top 0x730000, reserve_size 389120, 
allocsize"

Hope this can help

Original comment by JCerwin...@gmail.com on 21 May 2010 at 3:42

GoogleCodeExporter commented 8 years ago
Wow, thanks for the tips, JCerwinske!

Original comment by medgar123 on 21 May 2010 at 7:42

GoogleCodeExporter commented 8 years ago

Original comment by medgar123 on 30 Jun 2010 at 9:18