On Mon 2019-10-28 (14:24), Christoph Moench-Tegeder wrote:
> My analysis: screen dumps core on terminals with TERM=xterm* or
> TERM=rxvt* if they don't advertise Km ("key_mouse") capability
Ah great, many thanks and for the commit, and yes I had my TERM
set differently on the host.
___
## Gareth de Vaux (sta...@lordcow.org):
> $ screen
>
> [screen caught signal 11. (core dumped)]
Try this:
https://svnweb.freebsd.org/ports?view=revision&sortby=date&revision=515868
If that doesn't help, we'll need at least a backtrace.
Regards,
Christoph
--
Spare Space
__
That already had been reported here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241538 by Marcin.
My analysis: screen dumps core on terminals with TERM=xterm* or
TERM=rxvt* if they don't advertise Km ("key_mouse") capability
via termcap. A workaround is to set TERM to xterm-vt220 (which has
## Gareth de Vaux (sta...@lordcow.org):
> (there's no core dump).
ulimit -c
> This happens as a user or root, however screen runs fine on the host.
It coredumps here, too (on a 12.0-RELEASE) - I'm looking at it, there's
something fishy going on with the termcap data (the whole thing is
#define
Hi all, I upgraded from 11-STABLE r344000 to r353939 and now screen
(sysutils/screen)
crashes inside both my jails:
$ screen
[screen caught signal 11. (core dumped)]
(there's no core dump).
kernel log:
pid 56569 (screen), jid 2, uid 1001: exited on signal 6
This happens as a user or root,
