Bug#392780: screen hangs at startup, child process segfaults
Hello, it's working in an upgraded etch machine, so that issue is no longer really importand for us. Thanks, Hermann -- Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg IWR; INF 368; 69120 Heidelberg; Tel: (06221)54-8236 Fax: -5224 Email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392780: screen hangs at startup, child process segfaults
Hi, (taking over maintainership from Adam) is there any news regarding this bug? Is it still reproducible? If so, have you been able to discern a pattern on which hosts it fails? Or have you upgraded to Etch in the meantime? Regards, Jan signature.asc Description: Digital signature
Bug#392780: screen hangs at startup, child process segfaults
On Fri, Oct 13, 2006 at 11:08:27AM -0700, Adam Lazur wrote: You may have to gdb as root to get a core because screen is setgid. screen works perfectly if you run it as root - so thats no way to debug the problem. If I start as user in gdb, the following happened: (gdb) run Starting program: /usr/bin/screen (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912505525408 (LWP 2672)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Directory '/var/run/screen' must have mode 777. Program exited with code 01. But if I change /var/run/sreen to that mode: /usr/bin/screen Directory '/var/run/screen' must have mode 775. Strange... As another datapoint: on an opteron with libc6 2.3.2.ds1-22sarge3 and passwd 1:4.0.3-31sarge8 screen works, but not on two machines with the latest security updates. Any ideas ? Greetings Hermann -- Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg IWR; INF 368; 69120 Heidelberg; Tel: (06221)54-8236 Fax: -5224 Email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392780: screen hangs at startup, child process segfaults
Package: screen Version: 4.0.2-4.1 Severity: important screen hangs on start, in the process list you see a defunct child process and in dmesg the following line appears: screen[16884]: segfault at 00f0 rip 2b5dfe3b rsp 7ff89100 error 4 I tried to get a core dump or strace to look further into the problem, but without luck. Thanks for any idea, greetings Hermann -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.15.6 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages screen depends on: ii base-passwd 3.5.9 Debian base system master password ii debconf 1.4.30.13 Debian configuration management sy ii libc6 2.3.2.ds1-22sarge4 GNU C Library: Shared libraries an ii libncursesw5 5.4-4 Shared libraries for terminal hand ii libpam0g 0.76-22Pluggable Authentication Modules l ii passwd1:4.0.3-31sarge9 change and administer password and -- debconf information: screen/old_upgrade_prompt: false -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
