public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Larry Hall <cygwin-lh@cygwin.com>
To: Michael Brand <cygwin@brand.scso.com>, cygwin@cygwin.com
Subject: Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1
Date: Mon, 23 Feb 2004 21:18:00 -0000	[thread overview]
Message-ID: <6.0.1.1.0.20040223143346.03a1c7e0@127.0.0.1> (raw)
In-Reply-To: <1077554594.403a2da21a1ef@scso.com>

At 11:43 AM 2/23/2004, Michael Brand you wrote:
>Hello,
>
>Regarding your question, Corinna, I am using Cygwin's latest stable (the one 
>you get when you download <http://www.cygwin.com/setup.exe> and install current 
>versions of packages). I am considerably more interested in a stable system 
>than in a "state-of-the-art" system, which is why I am avoiding the use of 
>snapshots.
>
>However, I have other developments regarding this problem:
>I have managed to reproduce the problem now in a "bash" script as well. It 
>still uses plenty of "sed"s, but the hang happened in a call to "basename".
>
>I am beginning to believe that this problem has to do with a misbehavior of 
>Cygwin on dual-CPU machines / on Xeons / on dual-Xeon machines.
>
>Any feedback, but especially from people with experience using Cygwin on such 
>platforms, will be much appreciated.


This all sounds like problems that have been reported before against 1.5.7 
and have been subsequently fixed and available in snapshots.  If you have a
chance, it's worth the small effort to try out a snapshot to see if all
the problems you're seeing are resolved.  The current snapshots are very
close to what 1.5.8 will be.  However, you should either keep around the 
cygwin1.dll for 1.5.7 or be prepared to reinstall 1.5.7 via setup if you 
install a snapshot, just in case you notice more debilitating problems than
you notice in 1.5.7 (that's pretty unlikely but it's always good to have a 
backup plan with software).  If you do try the snapshot, please let the list
know if it solves your problems and if you see any other problems not 
already reported.


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
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/

  reply	other threads:[~2004-02-23 19:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23 14:25 Michael Brand
2004-02-23 15:59 ` Corinna Vinschen
2004-02-23 17:26 ` Michael Brand
2004-02-23 21:18   ` Larry Hall [this message]
2004-02-24 15:47     ` Michael Brand
2004-02-24 17:00       ` Michael Brand
2004-02-24 17:59         ` Michael Brand
2004-02-24 18:03         ` Christopher Faylor
2004-02-24 17:11       ` Christopher Faylor
2004-02-24 19:46 Michael Brand
2004-02-25 19:14 Michael Brand
2004-02-25 20:57 ` Larry Hall
2004-03-04 13:53 Michael Brand
2004-03-04 17:25 ` Christopher Faylor
2006-02-13 22:19 Stewart Midwinter
2006-02-14  1:33 ` Christopher Faylor
     [not found] ` <43F174FF.1040102@brand.scso.com>
2006-02-14 17:35   ` Stewart Midwinter

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=6.0.1.1.0.20040223143346.03a1c7e0@127.0.0.1 \
    --to=cygwin-lh@cygwin.com \
    --cc=cygwin@brand.scso.com \
    --cc=cygwin@cygwin.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).