After some trials with Cygwin 2.1.0, it appears:
mintty 2.1.2 call fails under Windows 8.
mintty 2.1.2 call succeed under Windows 7.
Could you let me knwow when package 64bits will be available for further
trials?
Regards,
K'ptain
--
View this message in context:
http://cygwin.1069669.n5.n
Am 27.07.2015 um 20:08 schrieb Buchbinder, Barry (NIH/NIAID) [E]:
Thomas Wolff sent the following at Thursday, July 23, 2015 6:15 PM
mintty 2.1.2 is an update in response to a number of crash reports under
unclear circumstances; mintty only detaches from the caller's terminal
if the option -D is
> On Jul 27 22:44, Houder wrote:
>> > On Jul 27 19:44, Thomas Wolff wrote:
>> >> Am 27.07.2015 um 17:58 schrieb Houder:
>> >> >Hi Thomas,
>> >> >
>> >> >Moving load_dwm_funcs() did the trick ...
>> >> >
>> >> >
>> >> Thanks again for your analysis.
>> >> In Control Panel â Performance Informat
On Jul 27 22:44, Houder wrote:
> > On Jul 27 19:44, Thomas Wolff wrote:
> >> Am 27.07.2015 um 17:58 schrieb Houder:
> >> >Hi Thomas,
> >> >
> >> >Moving load_dwm_funcs() did the trick ...
> >> >
> >> >
> >> Thanks again for your analysis.
> >> In Control Panel â Performance Information and Tools
>> On Jul 27 19:44, Thomas Wolff wrote:
>>> Am 27.07.2015 um 17:58 schrieb Houder:
>>> >Hi Thomas,
>>> >
>>> >Moving load_dwm_funcs() did the trick ...
>>> >
>>> >
>>> Thanks again for your analysis.
>>> In Control Panel â Performance Information and Tools â Adjust visual
>>> effects,
>>> it is
> On Jul 27 19:44, Thomas Wolff wrote:
>> Am 27.07.2015 um 17:58 schrieb Houder:
>> >Hi Thomas,
>> >
>> >Moving load_dwm_funcs() did the trick ...
>> >
>> >
>> Thanks again for your analysis.
>> In Control Panel â Performance Information and Tools â Adjust visual
>> effects,
>> it is only the l
On Jul 27 19:44, Thomas Wolff wrote:
> Am 27.07.2015 um 17:58 schrieb Houder:
> >Hi Thomas,
> >
> >Moving load_dwm_funcs() did the trick ...
> >
> >
> Thanks again for your analysis.
> In Control Panel → Performance Information and Tools → Adjust visual
> effects,
> it is only the last of the flags
Thomas Wolff sent the following at Thursday, July 23, 2015 6:15 PM
>mintty 2.1.2 is an update in response to a number of crash reports under
>unclear circumstances; mintty only detaches from the caller's terminal
>if the option -D is given
Neither man mintty nor mintty --help document the new -D o
Am 27.07.2015 um 17:58 schrieb Houder:
Hi Thomas,
Moving load_dwm_funcs() did the trick ...
Thanks again for your analysis.
In Control Panel → Performance Information and Tools → Adjust visual
effects,
it is only the last of the flags, ☐ Use visual styles on windows and
buttons,
that makes
Hi Thomas,
Moving load_dwm_funcs() did the trick ...
Tested on 32-bits and 64-bits, W7
See appendix (winmain.c)
Henri// win.c (part of mintty)
// Copyright 2008-13 Andy Koppe
// Based on code from PuTTY-0.60 by Simon Tatham and team.
// Licensed under the terms of the GNU General Public License
> Hi Thomas,
>
> Let me rephrase/summarize my findings:
>
> Executing 'mintty -D' (i.e. v212)
>
> from a shortcut to bash (i.e. Cygwin console),
>
> will fork itself, where the child will turn itself into a session leader, as
> desired.
>
> i.e. the following code will be executed:
>
> #if 1 //
> On Sat, Jul 25, 2015 at 10:15 PM, Houder wrote:
> ...
>> Please, make a mental picture of the check boxes at your place at 'control
>> panel >
>> performance information and tools > adjust visual effects'.
>>
>> I'll bet, all check boxes for "eye candy" has been checked at your place;
>> NONE
On Sat, Jul 25, 2015 at 10:15 PM, Houder wrote:
...
> Please, make a mental picture of the check boxes at your place at 'control
> panel >
> performance information and tools > adjust visual effects'.
>
> I'll bet, all check boxes for "eye candy" has been checked at your place;
> NONE of
> them
> Hi, thank you very much for this analysis which should enable me to do
> further investigation; first, I'd like to know whether the two alternative
> codelets for the -D option change anything.
> Anyway, maybe I should simply disable transparency, either at all (but
> people would complain, I'm s
Am 26.07.2015 um 13:58 schrieb Houder:
...
Hi, thank you very much for this analysis which should enable me to do
further investigation; first, I'd like to know whether the two
alternative codelets for the -D option change anything.
Anyway, maybe I should simply disable transparency, either at
> Hi Thomas,
>
> Additionally ...
>
>> But first things, first ...
>>
>> Please, make a mental picture of the check boxes at your place at 'control
>> panel >
>> performance information and tools > adjust visual effects'.
>>
>> I'll bet, all check boxes for "eye candy" has been checked at your pla
Hi Thomas,
Additionally ...
> But first things, first ...
>
> Please, make a mental picture of the check boxes at your place at 'control
> panel >
> performance information and tools > adjust visual effects'.
>
> I'll bet, all check boxes for "eye candy" has been checked at your place;
> NONE o
> I found the bug (more or less): it is me (AND you). More will follow soon.
Hi Thomas,
As I reported earlier, I found the culprit ...
No, I did not build my own Cygwin.dll, as advised by Corinna, because to her
Cygwin
is NOT "rocket science" (after all these years), however to me, it is still
>> Hi Thomas,
>>> Maybe setsid() should not be called if fork() fails...
>>> Could you try this please:
>>> if (daemonize && !isatty(0)) {
>>> int pid = fork();
>>> if (pid > 0) exit(0);// exit parent process
>>> if (pid == 0) setsid(); // detach child process
>>> i
Am 24.07.2015 um 15:18 schrieb Houder:
Hi Thomas,
Maybe setsid() should not be called if fork() fails...
Could you try this please:
if (daemonize && !isatty(0)) {
int pid = fork();
if (pid > 0) exit(0);// exit parent process
if (pid == 0) setsid(); // detach child proc
On Jul 24 15:18, Houder wrote:
> Hi Thomas,
>
> >>> mintty 2.1.2 is an update in response to a number of crash reports under
> >>> unclear circumstances;
> > To resolve this discomforting issue which I still cannot reproduce,
> > could please those who experience a crash report some details about
> As I wrote 'and I asked myself', I was wondering about something like:
> 'getpid() != 1'
s/getpid/getppid/
Henri
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: h
On Jul 24 13:40, Thomas Wolff wrote:
> I wanted to check ttyname() for "/cons" but surprisingly ttyname() was null
> when started from cygwin console;
Isn't mintty a "subsystem=windows" application which is supposed to
attach or create a console at some later point? Maybe that's the
reason. Off
Hi Thomas,
>>> mintty 2.1.2 is an update in response to a number of crash reports under
>>> unclear circumstances;
> To resolve this discomforting issue which I still cannot reproduce,
> could please those who experience a crash report some details about
> their calling environment?
> Could the is
On 24.07.2015 09:50, Houder wrote:
mintty 2.1.2 is an update in response to a number of crash reports under
unclear circumstances;
To resolve this discomforting issue which I still cannot reproduce,
could please those who experience a crash report some details about
their calling environment?
C
> mintty 2.1.2 is an update in response to a number of crash reports under
> unclear circumstances;
> mintty only detaches from the caller's terminal if the option -D is given
Thank you, Thomas!
I extracted mintty.exe (and named it mintty-v212.exe) from
mintty-2.1.2-0.tar.xz, and
placed it in /b
26 matches
Mail list logo
