newsGNU Screen - News: Screen users mailing list

 
 
Latest News
GNU Screen v.4.9.0 posted by anaumov, Tue 01 Feb 2022 04:21:34 PM UTC - 0 replies
GNU Screen v.4.8.0 posted by amade, Wed 05 Feb 2020 08:48:18 PM UTC - 0 replies
GNU Screen v.4.7.0 posted by amade, Tue 01 Oct 2019 10:47:49 PM UTC - 0 replies
GNU Screen v.4.6.1 posted by amade, Mon 10 Jul 2017 07:45:46 PM UTC - 0 replies
GNU Screen v.4.6.0 posted by amade, Wed 28 Jun 2017 07:01:57 PM UTC - 0 replies
[Submit News]
[15 news in archive]

Screen users mailing list

Item posted by Juergen Weigert <jnweiger> on Fri 28 May 2004 12:37:45 PM UTC.

The mailing list mailto:screen-users@gnu.org, archived at http://mail.gnu.org/archive/html/screen-users is active again.

Screen 4.00.03, frozen, can't reattach (posted by Timothy Miller, Sat 20 Nov 2010 10:19:33 PM UTC)

When using gnu screen, I'm in the habit of just dropping the connection (I'll put my laptop to sleep, for example), and periodically, I have screen just refuse to allow me to reattach.  I've tried to do some research on this.

This guy claims to have submitted a patch to fix it:
http://churchturing.org/w/screen/

While this thread claims that there is no good fix:
http://www.mail-archive.com/screen-users@gnu.org/msg02595.html

I've tried all sorts of things to get it unstuck.  Attaching/detaching a debugger, various command-line options, sending signals, etc.  Nothing works.

My situation seems different from the 2009 thread, because I'm not stuck in write().  Here's what the debugger tells me:

0x00007f59953073c3 in __select_nocancel () at ../sysdeps/unix/syscall-template.S:82
82 ../sysdeps/unix/syscall-template.S: No such file or directory.
in ../sysdeps/unix/syscall-template.S
(gdb) where
#0  0x00007f59953073c3 in __select_nocancel () at ../sysdeps/unix/syscall-template.S:82
#1  0x0000000000441ccc in sched () at sched.c:124
#2  0x00000000004062b0 in main (ac=<value optimized out>, av=<value optimized out>) at screen.c:1365

I'm assuming I found the right process, anyhow.  There are no zombie clients running, so I can't kill any of those.  This is the only process with 'screen' in the name:

millerti 12529     1  0 Nov03 ?        00:00:02 SCREEN

I haven't tried deleting the socket node, but since this seems to be a new problem, I thought it safer if I were to ask for advice before doing something that might make it impossible to find out what happened.

What should I do?

Thanks.


    

 

Back to the top


Powered by Savane 3.9