public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* GNU screen trouble
@ 2017-05-27 12:01 Andrey Repin
  2017-05-27 18:00 ` Dan Kegel
                   ` (3 more replies)
  0 siblings, 4 replies; 7+ messages in thread
From: Andrey Repin @ 2017-05-27 12:01 UTC (permalink / raw)
  To: All

Greetings, All!

# uname -a; screen --version; screen -admS mc-server-session
CYGWIN_NT-6.1 daemon2 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
Screen version 4.05.01 (GNU) 25-Feb-17

# screen -S mc-server-session -Q windows
<hangs infinitely>

If I SEGV the hung child, there's a stacktrace, though I don't know how useful
it is.
Anything I can do to help trace it down?

Stack trace:
Frame        Function    Args
000FFFF7CF0  0018005CC8C (000FFFFE3F4, 0000000F6A8, 0007785DD48, 000FFFFDE50)
000FFFF7D90  0018005E25B (00000000000, 00000000000, 000000001A4, 00000000000)
000FFFF7FE0  0018011E383 (00600000610, 000001F0180, 0018030B218, 0018030C1C0)
000FFFF82D0  0018011B0AE (000FFFF8570, 00000000000, 00000000000, 000FFFF8250)
000FFFF84D0  0018011B539 (0018018F3B2, 00000000000, 000FFFF82F0, 00000000006)
000FFFF84D0  0018011B6EA (0018021D49F, 00180047D70, 00000000000, 0000000000B)
000FFFF84D0  0018011B99F (7B007F00030003, 0000000000B, 00100453035, 65657263735B0A0D)
000FFFF84D0  00100401335 (00805010004, 000006162C0, 000FFFF8560, 00000000001)
000FFFF84D0  0018005E25B (00000000001, 00000000000, 00000000002, 00000000000)
000FFFF8840  00180116E80 (00000000001, 00000000000, 00000000002, 00000000000)
000FFFF8840  00100423C76 (00000000001, 00000000000, 00000000002, 00000000000)
End of stack trace


-- 
With best regards,
Andrey Repin
Saturday, May 27, 2017 14:08:17

Sorry for my terrible english...


--
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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GNU screen trouble
  2017-05-27 12:01 GNU screen trouble Andrey Repin
@ 2017-05-27 18:00 ` Dan Kegel
  2017-05-30 19:33   ` Andrew Schulman
  2017-06-18 18:50 ` Andrey Repin
                   ` (2 subsequent siblings)
  3 siblings, 1 reply; 7+ messages in thread
From: Dan Kegel @ 2017-05-27 18:00 UTC (permalink / raw)
  To: cygwin

On Sat, May 27, 2017 at 4:27 AM, Andrey Repin <anrdaemon@yandex.ru> wrote:
> # uname -a; screen --version; screen -admS mc-server-session
> CYGWIN_NT-6.1 daemon2 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
> Screen version 4.05.01 (GNU) 25-Feb-17
>
> # screen -S mc-server-session -Q windows
> <hangs infinitely>

I see something similar:

$ uname -a
CYGWIN_NT-10.0 WIN10-BB-01 2.6.0(0.304/5/3) 2016-08-31 14:32 x86_64 Cygwin

buildbot@WIN10-BB-01 ~
$ apt-cyg install screen
$ screen --version
Screen version 4.04.00 (GNU) 19-Jun-16

$ screen
(inside the new screen:)
$ screen -Q info
(hangs 3 out of 4 tries so far)

On Linux, same sequence outputs stuff to stdout without hanging.

strace on cygwin shows
...
  204  185879 [main] screen 13324 fhandler_base::close: closing
'/tmp/uscreens/S-buildbot/16948.pty1.WIN10-BB-01-queryA' handle 0x288
  114  185993 [main] screen 13324 chmod: 0 =
chmod(/tmp/uscreens/S-buildbot/16948.pty1.WIN10-BB-01-queryA, 0600)
   94  186087 [main] screen 13324 getpid: 13324 = getpid()
   40  186127 [main] screen 13324 cygwin_listen: 0 = listen(3, 5)
   34  186161 [main] screen 13324 getpid: 13324 = getpid()
   34  186195 [main] screen 13324 fcntl64: fcntl(3, 6, ...)
   36  186231 [main] screen 13324 fhandler_socket::fcntl: owner set to 13324
   33  186264 [main] screen 13324 fcntl64: 0 = fcntl(3, 6, 0x340C)
   34  186298 [main] screen 13324 seteuid32: uid: 197609 myself->uid:
197609 myself->gid: 197121
   34  186332 [main] screen 13324 seteuid32: Nothing happens
   33  186365 [main] screen 13324 setegid32: new egid: 197121 current: 197121
   40  186405 [main] screen 13324 sigaction_worker: signal 19, newact
0xFFFF8800 (handler 0x100422520), oa 0xFFFF8680
   34  186439 [main] screen 13324 sigaction: 0 = sigaction(19,
0xFFFF8800, 0xFFFF87E0)
   34  186473 [main] screen 13324 sigaction_worker: signal 1, newact
0xFFFF8800 (handler 0x100422530), oa 0xFFFF8680
   34  186507 [main] screen 13324 sigaction: 0 = sigaction(1,
0xFFFF8800, 0xFFFF87E0)
   40  186547 [main] screen 13324 write: write(4, 0xFFFF8880, 12584)
  371  186918 [main] screen 13324 write: 12584 = write(4, 0xFFFF8880, 12584)
   75  186993 [main] screen 13324 close: close(4)
  157  187150 [main] screen 13324 fhandler_socket::close: 0 =
fhandler_socket::close()
   51  187201 [main] screen 13324 close: 0 = close(4)
   36  187237 [main] screen 13324 set_signal_mask: setmask 0, newmask
0, mask_bits 0
   33  187270 [main] screen 13324 handle_sigsuspend: oldmask 0x0, newmask 0x0

The hang is after that handle_sigsuspend line in the three times I've seen it,
right before screen would have printed Remove dead screens with 'screen -wipe'.

Seems highly repeatable, at least on my old install.
A little quality time with the source and maybe gdb would probably be
illuminating.
- Dan

--
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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GNU screen trouble
  2017-05-27 18:00 ` Dan Kegel
@ 2017-05-30 19:33   ` Andrew Schulman
  0 siblings, 0 replies; 7+ messages in thread
From: Andrew Schulman @ 2017-05-30 19:33 UTC (permalink / raw)
  To: cygwin

> On Sat, May 27, 2017 at 4:27 AM, Andrey Repin <anrdaemon@yandex.ru> wrote:
> > # uname -a; screen --version; screen -admS mc-server-session
> > CYGWIN_NT-6.1 daemon2 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
> > Screen version 4.05.01 (GNU) 25-Feb-17
> >
> > # screen -S mc-server-session -Q windows
> > <hangs infinitely>
> 
> I see something similar:
> 
> $ uname -a
> CYGWIN_NT-10.0 WIN10-BB-01 2.6.0(0.304/5/3) 2016-08-31 14:32 x86_64 Cygwin
> 
> buildbot@WIN10-BB-01 ~
> $ apt-cyg install screen
> $ screen --version
> Screen version 4.04.00 (GNU) 19-Jun-16
> 
> $ screen
> (inside the new screen:)
> $ screen -Q info
> (hangs 3 out of 4 tries so far)

Yeah, I see this too, in i686 and x86_64. No immediate ideas on a solution,
sorry. Andrew


--
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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GNU screen trouble
  2017-05-27 12:01 GNU screen trouble Andrey Repin
  2017-05-27 18:00 ` Dan Kegel
@ 2017-06-18 18:50 ` Andrey Repin
  2017-07-21 12:58 ` Andrey Repin
  2017-09-27 19:05 ` Andrey Repin
  3 siblings, 0 replies; 7+ messages in thread
From: Andrey Repin @ 2017-06-18 18:50 UTC (permalink / raw)
  To: All, cygwin

Greetings, All!

> # uname -a; screen --version; screen -admS mc-server-session
> CYGWIN_NT-6.1 daemon2 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
> Screen version 4.05.01 (GNU) 25-Feb-17

> # screen -S mc-server-session -Q windows
> <hangs infinitely>

> If I SEGV the hung child, there's a stacktrace, though I don't know how useful
> it is.
> Anything I can do to help trace it down?

> Stack trace:
> Frame        Function    Args
> 000FFFF7CF0  0018005CC8C (000FFFFE3F4, 0000000F6A8, 0007785DD48, 000FFFFDE50)
> 000FFFF7D90  0018005E25B (00000000000, 00000000000, 000000001A4, 00000000000)
> 000FFFF7FE0  0018011E383 (00600000610, 000001F0180, 0018030B218, 0018030C1C0)
> 000FFFF82D0  0018011B0AE (000FFFF8570, 00000000000, 00000000000, 000FFFF8250)
> 000FFFF84D0  0018011B539 (0018018F3B2, 00000000000, 000FFFF82F0, 00000000006)
> 000FFFF84D0  0018011B6EA (0018021D49F, 00180047D70, 00000000000, 0000000000B)
> 000FFFF84D0  0018011B99F (7B007F00030003, 0000000000B, 00100453035, 65657263735B0A0D)
> 000FFFF84D0  00100401335 (00805010004, 000006162C0, 000FFFF8560, 00000000001)
> 000FFFF84D0  0018005E25B (00000000001, 00000000000, 00000000002, 00000000000)
> 000FFFF8840  00180116E80 (00000000001, 00000000000, 00000000002, 00000000000)
> 000FFFF8840  00100423C76 (00000000001, 00000000000, 00000000002, 00000000000)
> End of stack trace

Anybody?


-- 
With best regards,
Andrey Repin
Sunday, June 18, 2017 21:35:24

Sorry for my terrible english...


--
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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GNU screen trouble
  2017-05-27 12:01 GNU screen trouble Andrey Repin
  2017-05-27 18:00 ` Dan Kegel
  2017-06-18 18:50 ` Andrey Repin
@ 2017-07-21 12:58 ` Andrey Repin
  2017-09-27 19:05 ` Andrey Repin
  3 siblings, 0 replies; 7+ messages in thread
From: Andrey Repin @ 2017-07-21 12:58 UTC (permalink / raw)
  To: Andrey Repin, cygwin

Greetings, Andrey Repin!

> Greetings, All!

> # uname -a; screen --version; screen -admS mc-server-session
> CYGWIN_NT-6.1 daemon2 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
> Screen version 4.05.01 (GNU) 25-Feb-17

> # screen -S mc-server-session -Q windows
> <hangs infinitely>

Still same problem after today's update of both Screen and cygwin.

> If I SEGV the hung child, there's a stacktrace, though I don't know how useful
> it is.
> Anything I can do to help trace it down?

> Stack trace:
> Frame        Function    Args
> 000FFFF7CF0  0018005CC8C (000FFFFE3F4, 0000000F6A8, 0007785DD48, 000FFFFDE50)
> 000FFFF7D90  0018005E25B (00000000000, 00000000000, 000000001A4, 00000000000)
> 000FFFF7FE0  0018011E383 (00600000610, 000001F0180, 0018030B218, 0018030C1C0)
> 000FFFF82D0  0018011B0AE (000FFFF8570, 00000000000, 00000000000, 000FFFF8250)
> 000FFFF84D0  0018011B539 (0018018F3B2, 00000000000, 000FFFF82F0, 00000000006)
> 000FFFF84D0  0018011B6EA (0018021D49F, 00180047D70, 00000000000, 0000000000B)
> 000FFFF84D0  0018011B99F (7B007F00030003, 0000000000B, 00100453035, 65657263735B0A0D)
> 000FFFF84D0  00100401335 (00805010004, 000006162C0, 000FFFF8560, 00000000001)
> 000FFFF84D0  0018005E25B (00000000001, 00000000000, 00000000002, 00000000000)
> 000FFFF8840  00180116E80 (00000000001, 00000000000, 00000000002, 00000000000)
> 000FFFF8840  00100423C76 (00000000001, 00000000000, 00000000002, 00000000000)
> End of stack trace




-- 
With best regards,
Andrey Repin
Friday, July 21, 2017 15:11:21

Sorry for my terrible english...


--
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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GNU screen trouble
  2017-05-27 12:01 GNU screen trouble Andrey Repin
                   ` (2 preceding siblings ...)
  2017-07-21 12:58 ` Andrey Repin
@ 2017-09-27 19:05 ` Andrey Repin
  2017-09-27 20:27   ` Andrey Repin
  3 siblings, 1 reply; 7+ messages in thread
From: Andrey Repin @ 2017-09-27 19:05 UTC (permalink / raw)
  To: Andrey Repin, cygwin

Greetings, Andrey Repin!

> # uname -a; screen --version; screen -admS mc-server-session
> CYGWIN_NT-6.1 daemon2 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
> Screen version 4.05.01 (GNU) 25-Feb-17

> # screen -S mc-server-session -Q windows
> <hangs infinitely>

> If I SEGV the hung child, there's a stacktrace, though I don't know how useful
> it is.
> Anything I can do to help trace it down?

Still an issue to an extent.

$ uname -a; screen --version; screen -admS mc-server-session
CYGWIN_NT-6.1 daemon2 2.9.0(0.318/5/3) 2017-09-12 10:18 x86_64 Cygwin
Screen version 4.06.01 (GNU) 10-Jul-17

$ screen -S mc-server-session -Q windows
<hangs>

This is running from mintty, results from cosole differs slightly, but I'm not
ready to explain it, I still can'[t get the pattern. But they aren't much more
useful compared to TTY runs.
I cn attach to a running session, often - list sessions, but unable to query
session information or send commands.

-- 
With best regards,
Andrey Repin
Wednesday, September 27, 2017 21:51:41

Sorry for my terrible english...


--
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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: GNU screen trouble
  2017-09-27 19:05 ` Andrey Repin
@ 2017-09-27 20:27   ` Andrey Repin
  0 siblings, 0 replies; 7+ messages in thread
From: Andrey Repin @ 2017-09-27 20:27 UTC (permalink / raw)
  To: Andrey Repin, cygwin

Greetings, Andrey Repin!

> # uname -a; screen --version; screen -admS mc-server-session
> CYGWIN_NT-6.1 daemon2 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
> Screen version 4.05.01 (GNU) 25-Feb-17

> # screen -S mc-server-session -Q windows
> <hangs infinitely>

> If I SEGV the hung child, there's a stacktrace, though I don't know how useful
> it is.
> Anything I can do to help trace it down?

Still an issue to an extent.

$ uname -a; screen --version; screen -admS mc-server-session
CYGWIN_NT-6.1 daemon2 2.9.0(0.318/5/3) 2017-09-12 10:18 x86_64 Cygwin
Screen version 4.06.01 (GNU) 10-Jul-17

$ screen -S mc-server-session -Q windows
<hangs>

This is running from mintty, results from cosole differs slightly, but I'm not
ready to explain it, I still can'[t get the pattern. But they aren't much more
useful compared to TTY runs.
I cn attach to a running session, often - list sessions, but unable to query
session information or send commands.

-- 
With best regards,
Andrey Repin
Wednesday, September 27, 2017 21:51:41

Sorry for my terrible english...


--
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

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2017-09-27 19:20 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-05-27 12:01 GNU screen trouble Andrey Repin
2017-05-27 18:00 ` Dan Kegel
2017-05-30 19:33   ` Andrew Schulman
2017-06-18 18:50 ` Andrey Repin
2017-07-21 12:58 ` Andrey Repin
2017-09-27 19:05 ` Andrey Repin
2017-09-27 20:27   ` Andrey Repin

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).