Consistent crash with all cygwin-based tools on XP SP2

Hello

I recently had to move to a new machine and am unable to compile any
Symbian code: all of the tools in %EPOCROOT%\Epoc32\gcc\bin crash on
start somewhere in cygwin1.dll. This holds both for the original
versions from Symbian (6.0, 6.1, 7.0s) as well as the ones from the gcc
improvement project. This is with a non-admin account, I don't have
access to an admin account right now.

I've checked that the exes are loading the right cygwin1.dll by running
them in a debugger as well as by renaming other cygwin1.dlls in the
system.

When I run, e.g., gcc.exe with no parameters, I get the 'gcc.exe has
encountered a problem and needs to close' dialog. If I debug, I see that
it crashes when dereference NULL+0x3e0 with the
(unreliable) stack trace of

	cygwin1.dll!_spawnvpe()  + 0x364	
  	cygwin1.dll!_dup2()  + 0x1cd	
  	cygwin1.dll!_dup2()  + 0xd2	
  	cygwin1.dll!_getpass()  + 0x1da9	
  	cygwin1.dll!_getpass()  + 0x204a	
  	cygwin1.dll!_select()  + 0x1a7c	
  	cygwin1.dll!_select()  + 0x1b9a	
  	cygwin1.dll!__assert()  + 0xd30	
  	cygwin1.dll!dll_crt0__FP11per_process()  + 0x27	
  	gcc.exe!00413ea2() 	
  	gcc.exe!0040103a() 	
  	kernel32.dll!_BaseProcessStart@4()  + 0x23	


So two questions:
1. Has anyone got a fix?
2. Has anyone got cygwin1.dbg for the 98r2 cygwin1.dll that I could see
more clearly what the problem is?

Thanks,

Hi

> I recently had to move to a new machine and am unable to compile any
> Symbian code: all of the tools in %EPOCROOT%\Epoc32\gcc\bin crash on
> start somewhere in cygwin1.dll. This holds both for the original
> versions from Symbian (6.0, 6.1, 7.0s) as well as the ones from the gcc
> improvement project. This is with a non-admin account, I don't have
> access to an admin account right now.
...
> So two questions:
> 1. Has anyone got a fix?
> 2. Has anyone got cygwin1.dbg for the 98r2 cygwin1.dll that I could see
> more clearly what the problem is?

We had this problem in our classroom PCs, until we noticed that running 
bldmake bldfiles once, with admin level account, solved the problem. We also 
downloaded the source for cygwin1.dll, recompiled it and if I remember 
correctly, this did the trick also (cannot remember surely, and do not know 
where the source was found since other guy tried to solve the problem by the 
recompilation).

-- Antti