X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4F7C20A5.80200@onevision.com> Date: Wed, 04 Apr 2012 12:21:25 +0200 From: Roland Schwingel User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: 1.7.12 breaks stdout of upx packed executables Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-15; format=flowed Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Hi... Just updated to 1.7.12 and found one regression. If you have upx packed executables (upx from cygwin distribution) the stdout of the packed executable is broken now. Try the following from mintty: upx --best /usr/bin/tar.exe -o /tmp/tar.exe /tmp/tar.exe You will notice that when you invoke the compressed /tmp/tar.exe that no output will be sent to the mintty console, while it works if you just invoke /usr/bin/tar.exe It works just fine with 1.7.11. When you decompress the executable using upx -d it will start to work again. This is not specific to tar, but to any exe I have seen right now. Strange, Roland -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple