From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: xman 1.1.5-1 immediately terminates with 'buffer overflow detected'
Date: Sun, 22 Dec 2019 11:21:00 -0000 [thread overview]
Message-ID: <749aa1d8-700b-8871-12b2-eab159dd0007@SystematicSw.ab.ca> (raw)
In-Reply-To: <098dccde-6dde-6301-b020-b457c5cc5f05@comcast.net>
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
next prev parent reply other threads:[~2019-12-22 5:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 5:44 Ken
2019-12-22 6:00 ` bzs
2019-12-22 11:21 ` Brian Inglis [this message]
2019-12-23 5:06 ` Ken
2019-12-23 23:27 ` Ken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=749aa1d8-700b-8871-12b2-eab159dd0007@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).