Mail Archives: cygwin/2005/12/12/05:32:47
On Dec 8 16:08, David Rothenberger wrote:
> ----------------------------------------------------------------------
> Problem 1:
> ----------------------------------------------------------------------
> With the 20051207 snapshot, I'm getting
> recreate_mmaps_after_fork_failed errors from XEmacs. To reproduce:
>
> >From a CMD.EXE shell:
>
> c:\cygwin\bin\bash -lc '/bin/xemacs -q'
>
> Then, Alt-X "shell-command" "env"
>
> This yields the following messages to the CMD.EXE shell. The "env"
> command never succeeds.
>
> 20 [main] xemacs 4148 fixup_mmaps_after_fork: ReadProcessMemory failed for MAP_PRIVATE address 0x1980000, Win32 error 998
> c:\cygwin\bin\xemacs-21.4.18.exe (4148): *** recreate_mmaps_after_fork_failed
>
> I don't have this problem with the 20051130 snapshot.
Thanks, this should be fixed in CVS now.
> ----------------------------------------------------------------------
> Problem 2:
> ----------------------------------------------------------------------
> This is also with XEmacs. I normally start XEmacs with the following
> command from a CMD.EXE shell:
>
> c:\cygwin\bin\bash -lc 'setsid xemacs &'
>
> If you try that with 'setsid xemacs -q &' and then type
>
> Alt-X "grep" "grep -ni system /etc/passwd"
>
> there is no result. Furthermore, typing in XEmacs yields red
> squares. XEmacs is essentially useless and must be restarted.
>
> I see this behavior with the 20051130 snapshot. It works with the
> 20051118 snapshot but pops a console window when running grep. It
> works correctly with the 20051110 snapshot.
You're obviously expecting that we know xemacs. I don't since I never
used it. Fortunately the above "env" problem was easily reproducible.
But I can't reproduce this grep problem since I'm unable to start the
above grep. The grep submenu is entirely greyed out when I look into
it. And furthermore I have no idea what a red square means in xemacs.
Isn't it possible to have easier testcases than (x)emacs of all things?
> ----------------------------------------------------------------------
> Problem 3:
> ----------------------------------------------------------------------
> >From a CMD.EXE shell:
>
> c:\cygwin\rxvt -e /bin/bash -li
> % ssh localhost
>
> The command succeeds but opens a console window while the SSH
> process is running.
>
> The console window doesn't open if I start bash first:
> c:\cygwin\bash -lc '/bin/rxvt -e /bin/bash -li'
> % ssh localhost
>
> The first command doesn't yield a console window with the 20051110
> snapshot, but does with 20051118 and 20051130.
>
> cygcheck output from the 20051207 snapshot is attached.
Works fine for me with current CVS. No extra console window at all.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -