This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: problems interrupting cygcheck -c on 20050104 snapshot
- From: Yitzchak Scott-Thoennes <sthoenna at efn dot org>
- To: cygwin at cygwin dot com
- Date: Tue, 1 Feb 2005 23:21:20 -0800
- Subject: Re: problems interrupting cygcheck -c on 20050104 snapshot
- Organization: bs"d
- References: <20050106021410.GA4068@efn.org> <20050106040513.GA7317@trixie.casa.cgf.cx> <20050106044026.GB2100@efn.org> <20050131170016.GC22449@trixie.casa.cgf.cx>
On Mon, Jan 31, 2005 at 12:00:16PM -0500, Christopher Faylor wrote:
> On Wed, Jan 05, 2005 at 08:40:26PM -0800, Yitzchak Scott-Thoennes wrote:
> >On Wed, Jan 05, 2005 at 11:05:13PM -0500, Christopher Faylor <cgf-no-personal-reply-please@cygwin.com> wrote:
> >> On Wed, Jan 05, 2005 at 06:36:02PM -0800, Yitzchak Scott-Thoennes wrote:
> >> >Using the 20050104 snapshot, running cygcheck -c from bash in a
> >> >console window with tty set and hitting control-C or kill'ing the
> >> >process (from another window) results in a burst of garbage to the
> >> >screen, and cygcheck -c continues on.
> >>
> >> Can't duplicate it. Sorry.
> >
> >Rats. It doesn't happen in rxvt or without tty.
> >
> >> There hasn't been any changes in signal handling in some time so I don't
> >> know why this snapshot should behave differently than any of the previous
> >> snapshots.
> >>
> >> Were you seeing the same behavior in previous snapshots?
> >
> >Don't know, but will check.
Oops, this one fell of the end of my todo list, sorry.
> Just checking. Are you still seeing this behavior?
No, IIRC it's been better since shortly after that, maybe the 20050106
snapshot. If it's important, I can go back and check.
--
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/