12:59 a.m.
Thanks for the reply.
I tried the suggested command, M-! test testfile.txt after first opening testfile.txt into
a buffer. I got the same "Doing fork: Bad file descriptor" message.
It would seem that this result is consistent with the hypothesis. How would I adjust the
path used by this version of xemacs?
In answering the questions asked of me, I am a new user of Xemacs and Cygwin, although I
have some experience with Linux and FreeBSD. As mentioned before, I am using the
"C:\cygwin\usr\local\bin\i686-pc-cygwin\xemacs-21.4.13.exe" binary for xemacs. I
used the Cygwin setup.exe version 2.416 to install cygwin, but I can't figure out
which version of cygwin I am using.
The funny thing is, though, that on another system I installed the same thing and it
worked. The big differences between the two systems are:
- I built the working system, whereas my Info Manag dept. built the one that doesn't
work
- The working system is a stand alone, but the broken one is part of a domain.
I am beginning to think that some form of the mkpasswd command might help me, but
Again, I really don't know what kinds of things to do to try an troubleshoot this
problem, so any suggestions are greatly welcome.
Stephen J. Turnbull wrote:
>>>>>"Eric" == Eric Nute
<eric(a)lybrandnute.net> writes:
>>>>>
>>>>>
Eric> I am using Xemacs, Cygwin version, on a Windows 2000
Eric> station. When I tried to use the tools, specifically "Tools
Eric> -> Compare -> Two Files" or "Tools -> Grep -> Grep all
files
Eric> in directory", the tool fails with an error in the bottom
Eric> line stating "Doing Fork: Bad File Descriptor" .
What happens if you do M-! grep something some-existing-file RET?
I suspect grep is not on the PATH that XEmacs knows about.
The other possibility is breakage in XEmacs handing off processes to
Cygwin. What version of Cygwin are you using? Is this changed
behavior, or are you a new XEmacs users? Have you updated (from a
previous version) either XEmacs or Cygwin lately?
A better place to ask is xemacs-beta(a)xemacs.org, and/or
xemacs-winnt(a)xemacs.org (the latter is nearly defunct, but there are
still a few subscribers who haven't joined the xemacs-beta list yet).
--
Eric Nute <eric(a)lybrandnute.net>
1:34 a.m.
New subject: Getting "Doing Fork: Bad File Descriptor" when using various tools
Eric Nute <eric(a)lybrandnute.net> writes:
I used the Cygwin setup.exe version 2.416 to install cygwin, but I
can't figure out which version of cygwin I am using.
In a bash window:
$ uname -a
The version of setup shouldn't matter. I can't reproduce your problem
here. I set PATH in my .profile and run XEmacs from a bash window.
Jon
--
But if serving the LORD seems undesirable to you, then choose for
yourselves this day whom you will serve . . . But as for me and my
household, we will serve the LORD.
-- Joshua 24:15 (NIV)
9:42 a.m.
New subject: Getting "Doing Fork: Bad File Descriptor" when using various tools
>>>> "Eric" == Eric Nute
<eric(a)lybrandnute.net> writes:
Eric> Thanks for the reply.
Eric> I tried the suggested command, M-! test testfile.txt after first opening
testfile.txt into a buffer. I got the same "Doing fork: Bad file descriptor"
message.
(setq debug-on-signal t)
(setq debug-on-quit t)
(setq debug-on-error t)
Provoke the error again.
Send us the *Backtrace* buffer contents.
Eric> It would seem that this result is consistent with the hypothesis. How would I
adjust the path used by this version of xemacs?
Set up the PATH variable. This even works in my native Windows XEmacs.
Eric> In answering the questions asked of me, I am a new user of Xemacs and Cygwin,
although I have some experience with Linux and FreeBSD. As mentioned before, I am using
the "C:\cygwin\usr\local\bin\i686-pc-cygwin\xemacs-21.4.13.exe" binary for
xemacs. I used the Cygwin setup.exe version 2.416 to install cygwin, but I can't
figure out which version of cygwin I am using.
Eric> The funny thing is, though, that on another system I installed the same thing
and it worked. The big differences between the two systems are:
Eric> - I built the working system, whereas my Info Manag dept. built the one that
doesn't work
Eric> - The working system is a stand alone, but the broken one is part of
Eric> a domain. I am beginning to think that some form of the mkpasswd
Eric> command might help me, but
Eric> Again, I really don't know what kinds of things to do to try an
troubleshoot this problem, so any suggestions are greatly welcome.
Eric> Stephen J. Turnbull wrote:
>>>>>> "Eric" == Eric
Nute <eric(a)lybrandnute.net> writes:
>>>>>>>
>>
Eric> I am using Xemacs, Cygwin version, on a Windows 2000
Eric> station. When I tried to use the tools, specifically "Tools
Eric> -> Compare -> Two Files" or "Tools -> Grep -> Grep all
files
Eric> in directory", the tool fails with an error in the bottom
Eric> line stating "Doing Fork: Bad File Descriptor" .
See above.
Hope this helps,
Adrian
>
> What happens if you do M-! grep something some-existing-file RET?
>
> I suspect grep is not on the PATH that XEmacs knows about.
>
> The other possibility is breakage in XEmacs handing off processes to
> Cygwin. What version of Cygwin are you using? Is this changed
> behavior, or are you a new XEmacs users? Have you updated (from a
> previous version) either XEmacs or Cygwin lately?
>
> A better place to ask is xemacs-beta(a)xemacs.org, and/or
> xemacs-winnt(a)xemacs.org (the latter is nearly defunct, but there are
> still a few subscribers who haven't joined the xemacs-beta list yet).
>
>
>
Eric> --
Eric> Eric Nute <eric(a)lybrandnute.net>
--
Adrian Aichner
mailto:adrianï¼ xemacs.org
http://www.xemacs.org/
7714
days inactive
7715
days old
2 comments
3 participants
participants (3)
-
Adrian Aichner -
Eric Nute -
Jon Ericson