From: John Wiersba <John.Wiersba@medstat.com>
To: cygwin users <cygwin@sourceware.cygnus.com>
Subject: RE: cat broken
Date: Wed, 30 Jun 1999 22:10:00 -0000 [thread overview]
Message-ID: <03F4742D8225D21191EF00805FE62B990205E17F@AA-MSG-01> (raw)
Message-ID: <19990630221000.nKdi0sVlXxjbEIdJWbjArzfc3Kv2WUcBat7sGBSTJG8@z> (raw)
> -----Original Message-----
> From: Earnie Boyd [ mailto:earnie_boyd@yahoo.com ]
> Sent: Thursday, June 24, 1999 1:57 PM
> To: cygwin users
> Subject: RE: cat broken
...<SNIP>...
> Let's restate this: It isn't cat that is broken but the
> terminal emulation
> within the cygwin dll.
OK, I believe this. the cygwin dll terminal emulation is fixed in the 6/10
release.
> "Stable release"? Well all of the snapshots are ALPHA
> untested releases. If a
> user suggests that he is using a particular snapshot without
> much headache it
> doesn't mean that there aren't bugs.
OK, I know this is still alpha or beta. Obviously there are still bugs.
What I'm looking for is *relative* stability, not perfection.
> If you're "experimenting" then you'd better have a "test
> plan" and a means of
> "fallback". NOTE: the cygwin-inst only contains binaries of
> importance to the
> maintenance and testing of the cygwin1.dll environment. Such
> things as mount,
> umount, cygwin1.dll, cygcheck, etc. and doesn't contain a
> full installation of
> pre-built binaries. The reason is that since the functions
> called from the
> cygwin1.dll are dynamic, then the binaries which use those
> functions don't need
> to be rebuilt to use the modified functions.
If what you say is correct (and I'm hoping it is!), then I do have a "test
plan": I simply throw away the broken version of cygwin1.dll and restore
the previous version.
> Therefore, IMO,
> the "trace
> thingies" are not a result of incompatibility between
> libraries and binaries;
> but, merely an inconvenient bug.
OK, then it appears that every snapshot since 5/24 has this bug in it. I'm
not exactly sure why it is showing up so frequently in my environment. I
saw this virtually every time when piping
ls | grep | perl
Could these two bugs be related? It seems that when the terminal emulation
bug went away, simultaneously the fhandler_base::fork_fixup bug appeared.
-- John
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-06-30 22:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-24 12:03 John Wiersba [this message]
1999-06-24 12:11 ` Chris Faylor
1999-06-30 22:10 ` Chris Faylor
1999-06-30 22:10 ` John Wiersba
-- strict thread matches above, loose matches on Subject: below --
1999-06-24 15:57 John Wiersba
1999-06-30 22:10 ` John Wiersba
1999-06-24 10:56 Earnie Boyd
1999-06-30 22:10 ` Earnie Boyd
1999-06-24 10:00 John Wiersba
1999-06-30 22:10 ` John Wiersba
1999-06-24 9:37 Phil Edwards
1999-06-30 22:10 ` Phil Edwards
1999-06-24 8:18 John Wiersba
1999-06-24 8:29 ` Dr. Volker Zell
1999-06-30 22:10 ` Dr. Volker Zell
1999-06-24 11:51 ` Chris Faylor
1999-06-30 22:10 ` Chris Faylor
1999-06-30 22:10 ` John Wiersba
1999-06-23 15:47 John Wiersba
1999-06-30 22:10 ` John Wiersba
1999-06-23 14:52 Phil Edwards
1999-06-30 22:10 ` Phil Edwards
1999-06-23 12:42 John Wiersba
1999-06-24 0:49 ` Dr. Volker Zell
1999-06-30 22:10 ` Dr. Volker Zell
1999-06-30 22:10 ` John Wiersba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03F4742D8225D21191EF00805FE62B990205E17F@AA-MSG-01 \
--to=john.wiersba@medstat.com \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).