screen-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[screen-devel] [bug #66158] Reading a screenrc leads to segfault in 5.0.


From: Alexander Naumov
Subject: [screen-devel] [bug #66158] Reading a screenrc leads to segfault in 5.0.0
Date: Fri, 6 Sep 2024 13:30:41 -0400 (EDT)

Follow-up Comment #2, bug #66158 (group screen):


> $ screen --version
> Screen version 5.0.0 (build on 2024-08-29 01:08:49)
> $ touch /tmp/screenrc
> $ file /tmp/screenrc
> /tmp/screenrc: empty
> $ screen -X source /tmp/screenrc
> * buffer overflow detected *: terminated
> Aborted (core dumped)

What OS do you use? How did you build screen?
Can you try to get the gdb stack from this segfault?


> Both commands were executed while an open and attached screen (socket).
Can you try to reproduce it without existing screen sessions?


> Originally I had a broken hard status, as in bug #66141, but by trying to
narrow down the origin discovered this potential common cause. I'll mention
this issue on the other bug, too.
Let's talk here about some concrete problem :)


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?66158>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]