* bash within XEmacs
@ 1999-07-01 13:52 Ian T Zimmerman
1999-07-02 10:48 ` Ian T Zimmerman
1999-07-31 18:34 ` Ian T Zimmerman
0 siblings, 2 replies; 4+ messages in thread
From: Ian T Zimmerman @ 1999-07-01 13:52 UTC (permalink / raw)
To: cygwin
I am still getting those pesky messages:
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1048 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1049 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1050 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1051 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1052 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1053 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1054 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
amazon:~$
And one more everytime a start a program from this shell. For extra
weirdness, this is not completely reproducible, sometimes it starts
cleanly, OTOH sometimes (rarely) it's DOA. I can discern no pattern
in the situations with various outcomes.
NT4 SP5, NTFS, binary mount, CYGWIN=tty ntea
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: bash within XEmacs
1999-07-01 13:52 bash within XEmacs Ian T Zimmerman
@ 1999-07-02 10:48 ` Ian T Zimmerman
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-31 18:34 ` Ian T Zimmerman
1 sibling, 1 reply; 4+ messages in thread
From: Ian T Zimmerman @ 1999-07-02 10:48 UTC (permalink / raw)
To: cygwin
I wrote:
Ian> I am still getting those pesky messages:
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1048 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1049 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1050 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1051 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1052 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1053 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1054 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> amazon:~$
Ian> And one more everytime a start a program from this shell. For extra
Ian> weirdness, this is not completely reproducible, sometimes it starts
Ian> cleanly, OTOH sometimes (rarely) it's DOA. I can discern no pattern
Ian> in the situations with various outcomes.
Ian> NT4 SP5, NTFS, binary mount, CYGWIN=tty ntea
I have since found I don't get the messages when I (setq
process-conection-type nil) in Xemacs (forcing it to use pipes instead
of ptys). So it is specific to fhandler_[pt]ty*. Of course
interacting through pipes is not really desirable and leads to other
problems.
What is interesting is the message refers to /dev/tty1 which shouldn't
be involved, it ought to be /dev/ttyp1 (if the virtual device names
are Unixy-sensible at all).
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: bash within XEmacs
1999-07-02 10:48 ` Ian T Zimmerman
@ 1999-07-31 18:34 ` Ian T Zimmerman
0 siblings, 0 replies; 4+ messages in thread
From: Ian T Zimmerman @ 1999-07-31 18:34 UTC (permalink / raw)
To: cygwin
I wrote:
Ian> I am still getting those pesky messages:
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1048 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1049 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1050 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1051 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1052 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1053 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> [main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1054 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
Ian> amazon:~$
Ian> And one more everytime a start a program from this shell. For extra
Ian> weirdness, this is not completely reproducible, sometimes it starts
Ian> cleanly, OTOH sometimes (rarely) it's DOA. I can discern no pattern
Ian> in the situations with various outcomes.
Ian> NT4 SP5, NTFS, binary mount, CYGWIN=tty ntea
I have since found I don't get the messages when I (setq
process-conection-type nil) in Xemacs (forcing it to use pipes instead
of ptys). So it is specific to fhandler_[pt]ty*. Of course
interacting through pipes is not really desirable and leads to other
problems.
What is interesting is the message refers to /dev/tty1 which shouldn't
be involved, it ought to be /dev/ttyp1 (if the virtual device names
are Unixy-sensible at all).
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* bash within XEmacs
1999-07-01 13:52 bash within XEmacs Ian T Zimmerman
1999-07-02 10:48 ` Ian T Zimmerman
@ 1999-07-31 18:34 ` Ian T Zimmerman
1 sibling, 0 replies; 4+ messages in thread
From: Ian T Zimmerman @ 1999-07-31 18:34 UTC (permalink / raw)
To: cygwin
I am still getting those pesky messages:
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1048 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1049 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1050 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1051 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1052 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1053 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
[main] d:\cygwin-b20\H-i586-cygwin32\bin\bash.exe 1054 (0) fhandler_base::fork_fixup: /dev/tty1 - error 6, handle 0x0
amazon:~$
And one more everytime a start a program from this shell. For extra
weirdness, this is not completely reproducible, sometimes it starts
cleanly, OTOH sometimes (rarely) it's DOA. I can discern no pattern
in the situations with various outcomes.
NT4 SP5, NTFS, binary mount, CYGWIN=tty ntea
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~1999-07-31 18:34 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-07-01 13:52 bash within XEmacs Ian T Zimmerman
1999-07-02 10:48 ` Ian T Zimmerman
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-31 18:34 ` Ian T Zimmerman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).