Date: Sat, 5 Apr 2014 15:08:04 +0200 (CEST) From: Kover Attila <koverat@freemail.hu> To: freebsd-arm@freebsd.org Subject: Re: screen(1) crashes plus weird output for screen -ls Message-ID: <freemail.20140405150804.40570.1@xmldata04>
next in thread | raw e-mail | index | archive | help
Hi,
I have some old RPi images which I was build (I use a modified image build =
script from kernelnomicon.org), the oldest is r252056 from June 2013. I was=
a distant memory that screen was worked some months ago, so I was booted t=
hat old image, compiled screen from ports (r350213, recently fetched with s=
vn) and the test shows that it is work with the old kernel version.
root@freepi:~ # screen -ls
There are screens on:
561.pts-0.freepi (Attached)
568.pts-2.freepi (Detached)
2 Sockets in /tmp/screens/S-root.
root@freepi:~ # uname -a
FreeBSD freepi 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r252056M: Fri Jun 21 17=
:59:17 CEST 2013 root@dlc-10c:/root/ujra/svnhead/obj/arm.armv6/root/ujr=
a/svnhead/head/sys/RPI-B-DRS arm
root@freepi:~ # screen --version
Screen version 4.00.03 (FAU) 23-Oct-06
root@freepi:~ #=20
Best Regards
Attila
> Hi,
>=20
> while working with screen(1) it dumps core very often on arm.
> Using gdb on the core shows
> (gdb) bt
> #0 0x2029bc18 in strlen () from /lib/libc.so.7
> #1 0x0001e9a4 in ?? ()
> (gdb)
> as the last function called every time.
>=20
> Interestingly the output of "screen -ls" is a little bit weird an looks
>=20
> There is a screen on:
> 814.ttyu0.rpi (Attached)
> -1073746664 Socket
> =C3=90 =C3=A1 in =C2=B0=C3=B5=C3=BF=C2=BF8=C3=A8.
>=20
> instead of the expected=20
>=20
> There is a screen on:
> 814.ttyu0.rpi (Attached)
> 1 Socket in /tmp/screens/S-root
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?freemail.20140405150804.40570.1>