Date: Mon, 9 Feb 2009 14:20:09 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Tried mintty but it locks-up on enabling "Copy on select"
Message-ID: <20090209192009.GA8970@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20090209091728.7b0a18a1.Rhubbell@iHubbell.com> <416096c60902091054l5664812bi8af7002f39648ec8@mail.gmail.com> <20090209111101.30ed33a2.Rhubbell@iHubbell.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090209111101.30ed33a2.Rhubbell@iHubbell.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Mon, Feb 09, 2009 at 11:11:01AM -0800, rhubbell wrote:
>On Mon, 9 Feb 2009 18:54:58 +0000
>Andy Koppe <andy.koppe@gmail.com> wrote:
>
>> > Maybe a known issue.
>> >
>> > Just tried mintty 0.3.5:
>> >
>> > Options->Mouse->Copy on select
>> >
>> > mintty becomes unresponsive and I have to kill it.
>> > The virtual set size goes to 450megabytes
>> 
>> That's a new one actually. Can you reproduce it? If it's not too much
>> bother, any details about the bug and your system would be
>> appreciated. The ~/.minttyrc file might be helpful too.
>
>Yes, it's reproducible. I just installed mintty and then ran it.
>So whatever mintty does to .minttyrc is what's in that file.
>
>I found a mintty.exe.stackdump
>Exception: STATUS_ACCESS_VIOLATION
>The stack trace is incomplete and ends with 
>(probably corrupted stack)

It's still possible that it would be useful though and if it's
truncated it can't be very long so go ahead and send it here.

cgf

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