child (xterm) fork failure as it loads to different address

2013-07-29 Thread Ariel Burbaickij
Hello group, I have a fresh installation of cygwin/ (cygcheck returns following for cygwin1.dll: cygwin1.dll - os=4.0 img=1.0 sys=4.0 cygwin1.dll v0.0 ts=2013-07-22 16:06)/cygwin-X (1.14.2-1 built 2013-07-08) and following happens: upon attempt to execute startxwin.exe get following error, while

Re: child (xterm) fork failure as it loads to different address

2013-07-29 Thread marco atzeri
Il 7/29/2013 10:10 AM, Ariel Burbaickij ha scritto: Hello group, I have a fresh installation of cygwin/ (cygcheck returns following for cygwin1.dll: cygwin1.dll - os=4.0 img=1.0 sys=4.0 cygwin1.dll v0.0 ts=2013-07-22 16:06)/cygwin-X (1.14.2-1 built 2013-07-08) and following happens: upon

Re: child (xterm) fork failure as it loads to different address

2013-07-29 Thread Ariel Burbaickij
OK, thank, you, so usual suspects. Now, removing, antivirus and stuff will not be possible in this particular environment but adjustments in the configuration are well possible, provided I will be able to prove to administrators that troubles, indeed, stem from antivirus and co. Now, I see in the

Re: child (xterm) fork failure as it loads to different address

2013-07-29 Thread Corinna Vinschen
On Jul 29 09:35, Ryan Johnson wrote: http://cygwin.com/acronyms/#TOFU On 29/07/2013 8:15 AM, Ariel Burbaickij wrote: OK, thank, you, so usual suspects. Now, removing, antivirus and stuff will not be possible in this particular environment but adjustments in the configuration are well

Re: child (xterm) fork failure as it loads to different address

2013-07-29 Thread Ryan Johnson
http://cygwin.com/acronyms/#TOFU On 29/07/2013 8:15 AM, Ariel Burbaickij wrote: OK, thank, you, so usual suspects. Now, removing, antivirus and stuff will not be possible in this particular environment but adjustments in the configuration are well possible, provided I will be able to prove to

Re: child (xterm) fork failure as it loads to different address

2013-07-29 Thread Ariel Burbaickij
So no, Windows NT will not work. Neither will Win95/98/2000. Nor will XP SP1/SP2. But if your admins are really so worried about viruses, they won't let you run those ancient operating systems anyway, because MS no longer pushes security patches for them. You misread, I am afraid. I am running

Re: child (xterm) fork failure as it loads to different address

2013-07-29 Thread Ariel Burbaickij
OK, for the record: looks like rebasing did help quite a bit here. /wbr Ariel Burbaickij On Mon, Jul 29, 2013 at 3:35 PM, Ryan Johnson ryan.john...@cs.utoronto.ca wrote: http://cygwin.com/acronyms/#TOFU On 29/07/2013 8:15 AM, Ariel Burbaickij wrote: OK, thank, you, so usual suspects. Now,