Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: CDB problem under bash shell Date: Fri, 29 Apr 2005 20:58:58 -0700 Message-ID: From: "Lauris, Eli" To: X-OriginalArrivalTime: 30 Apr 2005 03:58:58.0764 (UTC) FILETIME=[EFDC80C0:01C54D38] X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j3U3xA9d029800 No, I tried both CYGWIN=tty and CYGWIN=notty with no effect on the cdb behavior. Ei -----Original Message----- From: Christopher Faylor [mailto:cgf-no-personal-reply-please AT cygwin DOT com] Sent: Friday, April 29, 2005 7:50 PM To: cygwin AT cygwin DOT com Subject: Re: CDB problem under bash shell On Fri, Apr 29, 2005 at 06:44:28PM -0700, Lauris, Eli wrote: >Has anyone encountered the following problem when Microsoft CDB >(console debugger) is started from cygwin bash shell: CDB appears to >"eat" the last character of every command. I've tried various stty >settings such as onlret and onlcr and others, to no avail. > >This is happening on Windows Server 2003 running cygwin-1.5.12. > >If anyone has seen this problem and found a workaround, I'd really >appreciate hearing from you. Does setting CYGWIN=tty before starting bash cause any change in behavior? It could conceivably make things worse, but maybe CDB will work better when it thinks it has a pipe (aka cygwin tty) as stdin. 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/ -- 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/