From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 3.1.6
Date: Tue, 26 May 2020 16:49:18 +0200 [thread overview]
Message-ID: <0466e890-2d9b-4407-de5f-2786b7f33c88@towo.net> (raw)
In-Reply-To: <CAHdnY6P6Rc-o2K00koqMgBHLy6A6EKLTWwmbGY4VB9gzczB-Gw@mail.gmail.com>
Am 26.05.2020 um 16:30 schrieb David Dombrowsky via Cygwin:
> This version now coredumps on my machine. This is on a 32-bit
> machine. Is this the final nail in the coffin for 32-bit?
Of course not. Mintty actually still runs on Windows XP and even Windows
2000.
However, bugs happen and I guess you're running Windows 7 where 3.1.6
would crash. Fixed in the repository already.
Thomas
> [2000] davek@davek-win:~>mintty
> *** stack smashing detected ***: terminated
> Aborted (core dumped)
> Stack trace:
> Frame Function Args
> 0022C2CC 610239CC (0000023C, 0000EA60, 000000A4, 0022C33C)
> 0022C3FC 6110247A (0022C41C, 002FBFE0, 00000012, 0000000D)
> 0022C418 6112C582 (0000028E, 000303E9, 00000000, 00000000)
>
> [2006] davek@davek-win:~/winhome/Desktop>mintty --version
> mintty 3.1.6 (i686-pc-cygwin)
> © 2013/2019 Andy Koppe / Thomas Wolff
> License GPLv3+: GNU GPL version 3 or later
> There is no warranty, to the extent permitted by law.
>
> On Thu, May 21, 2020 at 2:28 PM Thomas Wolff <towo@towo.net> wrote:
>> I have uploaded mintty 3.1.6 with the following changes:
>>
>> Window handling
>> * Fixed resource leak when displaying images (#995).
>> * Fixed crash condition on keyboard auto-repeat (#996). (Apologies
>> for this one.)
>>
>> The homepage is at http://mintty.github.io/
>> It also links to the issue tracker.
>>
>> ------
>> Thomas
>> --
>> Problem reports: https://cygwin.com/problems.html
>> FAQ: https://cygwin.com/faq/
>> Documentation: https://cygwin.com/docs.html
>> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>
>
next prev parent reply other threads:[~2020-05-26 14:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 17:41 Thomas Wolff
2020-05-22 9:22 ` Takashi Yano
2020-05-22 10:14 ` Thomas Wolff
2020-05-22 11:01 ` Takashi Yano
2020-05-22 12:58 ` Takashi Yano
2020-05-22 13:54 ` Takashi Yano
2020-05-22 14:56 ` Takashi Yano
2020-05-22 20:16 ` Thomas Wolff
2020-05-26 14:30 ` David Dombrowsky
2020-05-26 14:49 ` Thomas Wolff [this message]
2020-05-26 15:15 ` Randall Nutz
2020-05-26 15:31 ` Thomas Wolff
[not found] ` <CAMVJNJuDbQ=Y5qCy=C8rUSaqnA+MXszrJqbAWdyM5YFfAK7Wdw@mail.gmail.com>
2020-05-26 17:14 ` Thomas Wolff
2020-05-26 19:16 ` Maarten Hoes
2020-05-26 19:53 ` Marco Atzeri
2020-05-26 20:18 ` Maarten Hoes
2020-05-26 20:36 ` Brian Inglis
2020-05-26 21:00 ` Maarten Hoes
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=0466e890-2d9b-4407-de5f-2786b7f33c88@towo.net \
--to=towo@towo.net \
--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).