This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: xman 1.1.5-1 immediately terminates with 'buffer overflow detected'
- From: Brian Inglis <Brian dot Inglis at SystematicSw dot ab dot ca>
- To: cygwin at cygwin dot com
- Date: Sat, 21 Dec 2019 22:44:57 -0700
- Subject: Re: xman 1.1.5-1 immediately terminates with 'buffer overflow detected'
- References: <098dccde-6dde-6301-b020-b457c5cc5f05@comcast.net>
- Reply-to: Brian dot Inglis at SystematicSw dot ab dot ca
On 2019-12-21 17:44, Ken wrote:
> Issue: xman 1.1.5-1 fails with 'buffer overflow detected'
> Cygwin versions tested: 3.1.2-1, 3.1.1-1, and 3.0.7-1
> OS: Windows 10 Pro 1903 (and also in Windows 7 Pro; tested only with cygwin 3.0.7)
> Attached is cygcheck.out of the package status.
> Details:
> I first noticed the xman package began failing when it was bumped from 1.1.4-1
> to 1.1.5-1 in cygwin 3.0.x.
> I confirmed that it still fails with cygwin 3.1.1-1 and 3.1.2-1 with fresh
> installations.
> $ xman
> *** buffer overflow detected ***: terminated
> Dropping back to xman 1.1.4-1 fixes the issue.
WJFFM W10 1809, Cygwin 3.0.7, xorg-server 1.20.4, xman 1.1.5:
$ uname -srvmo
CYGWIN_NT-10.0 3.0.7(0.338/5/3) 2019-04-30 18:08 x86_64 Cygwin
$ head /proc/version
CYGWIN_NT-10.0-17763 version 3.0.7-338.x86_64 (corinna@calimero) (gcc version
7.4.0 20181206 (Fedora Cygwin 7.4.0-1) (GCC) ) 2019-04-30 18:08 UTC
$ xman &
[1] 35536
browsie...browsie...browsie...browsie...browsie...browsie...browsie...browsie...Quit
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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