[ANNOUNCEMENT] Updated: mintty 3.1.6
Thomas Wolff
towo@towo.net
Tue May 26 17:14:00 GMT 2020
[including CC to the list again to catch-up for the discussion there;
and please remember not to "top-post" if you respond there]
Am 26.05.2020 um 18:53 schrieb Randall Nutz:
> I made several attempts on different installations.
> One is Version 10.0.10240 (32bit) On this one, right after reading
> your post indicating the repo was updated, I re-ran setup to update
> Mintty to the latest which shows to be 3.1.6-1. This version still
> dumped.
Repository refers to the github home of mintty
(https://github.com/mintty/mintty/), it's not yet a cygwin package.
You could download from there and compile a version.
> The other is Version 10.0.15063 (64bit).
Thanks for the info. Both versions are really *very* outdated. Yet it's
valuable to know certain things don't work there. Mintty will be adapted.
> I am unable to play around in this instance as I have an active user
> on it with a deadline.
> If/when I have time today, I'll create another one with this OS
> version and test it.
> /Randall
>
> On Tue, May 26, 2020 at 10:31 AM Thomas Wolff <towo@towo.net
> <mailto:towo@towo.net>> wrote:
>
> Am 26.05.2020 um 17:15 schrieb Randall Nutz:
>> I have had issues with 3.1.6 core dump crashes on Win7 32b, Win7
>> 64bit & Win10 both 32 & 64. I fought this all weekend.
> Please report the Windows 10 versions on which you experience
> this: cmd /c ver
>
>> I ended up rolling back to 3.1.4 (3.1.5 also dumped) all this
>> with Cygwin 32bit.
>> Unfortunately, we have an application that depends on 32 bit Cygwin.
> Don't worry, there are no plans to neglect 32-bit support in mintty.
> For your application, however, consider that cygwin 32-bit support
> seems to be fading in general as cygwin 32-bit is said to be less
> stable (due to library address conflicts), so it may be worth
> considering an upgrade of the application.
>
>
>> On Tue, May 26, 2020 at 10:05 AM Thomas Wolff <towo@towo.net
>> <mailto:towo@towo.net>> wrote:
>>
>> 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
>> <mailto: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
>> >
>> >
>>
>> --
>> 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
>>
>
More information about the Cygwin
mailing list