Greetings, Takashi Yano!
> On Sun, 2 Feb 2020 23:52:26 +0300
> Andrey Repin wrote:
>> Trying to rebase a newly unpacked Cygwin snapshot leads to
>> 0 [main] dash (220072) shared_info::initialize: size of shared memory region
>> changed from 50104 to 49080
>>
>> Any hints?
> Does not rebooting w
On Sun, 2 Feb 2020 23:52:26 +0300
Andrey Repin wrote:
> Trying to rebase a newly unpacked Cygwin snapshot leads to
> 0 [main] dash (220072) shared_info::initialize: size of shared memory region
> changed from 50104 to 49080
>
> Any hints?
Does not rebooting windows solve?
--
Takashi Yano
--
Greetings, All!
Trying to rebase a newly unpacked Cygwin snapshot leads to
0 [main] dash (220072) shared_info::initialize: size of shared memory region
changed from 50104 to 49080
Any hints?
--
With best regards,
Andrey Repin
Sunday, February 2, 2020 23:51:26
Sorry for my terrible english...
On Sun, 2 Feb 2020 13:18:03 +0100
m0viefreak wrote:
> On 02.02.2020 10:59, Takashi Yano wrote:
> >> 4) Importance of TERM: When connecting to my Cygwin installation using
> >>SSH using Putty, TERM=putty-256color is set. When executing non-
> >>native program from that session using that TER
On 2020-02-02 10:48, Anon User via cygwin wrote:
> OK I found it. You're right. The same outcome occurs. So I guess it's not
> cygwin specific. Sorry to have wasted your time. I guess my Windows install
> is messed up somehow. I wish I could get the feedback I need to figure out
> what I did
On 02.02.2020 10:59, Takashi Yano wrote:
> On Sat, 1 Feb 2020 19:00:04 +0100
> m0viefreak wrote:
>> Since Cygwin 3.1's pseudo console support was introduced I've run into
>> lots of issues with non-cygwin programs.
>
> Thanks for the report.
>
>> 1) Mangled output: See screenshot [1].
>>As
On Sat, 1 Feb 2020 19:00:04 +0100
m0viefreak wrote:
> Since Cygwin 3.1's pseudo console support was introduced I've run into
> lots of issues with non-cygwin programs.
Thanks for the report.
> 1) Mangled output: See screenshot [1].
>As you can see, at what it seems random places, the output i
OK I found it. You're right. The same outcome occurs. So I guess it's not
cygwin specific. Sorry to have wasted your time. I guess my Windows install
is messed up somehow. I wish I could get the feedback I need to figure out what
I did to have caused this. I have tried countless searches on
Sure. I'm willing to try it. Where do I get that compiler from?
--
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
On Sun, 2 Feb 2020 09:14:25 + (UTC)
"Anon User via cygwin" wrote:
> Not sure how to confirm that. I install the built-in OpenSSH client/server
> app. Then I start the OpenSSH server service. Then I ssh to 127.0.0.1 and
> login fine. There is no waiting on the service starting up nor on t
Not sure how to confirm that. I install the built-in OpenSSH client/server
app. Then I start the OpenSSH server service. Then I ssh to 127.0.0.1 and
login fine. There is no waiting on the service starting up nor on the ssh
client connecting to the daemon and getting a shell (Windows 'DOS' s
On Sun, 2 Feb 2020 08:31:51 + (UTC)
"Anon User via cygwin" wrote:
> Same behavior as mintty, tmux, the previous test case, with TaskManager's
> analyze wait chain saying it's waiting on Network I/O.
>
> $ ./a.exeStarted.
> ** 1 min wait here **
> CreatePseudoConsole() end.ClosePseudoConsole(
Same behavior as mintty, tmux, the previous test case, with TaskManager's
analyze wait chain saying it's waiting on Network I/O.
$ ./a.exeStarted.
** 1 min wait here **
CreatePseudoConsole() end.ClosePseudoConsole() end.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
13 matches
Mail list logo