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: anonymous
Subject: [screen-devel] [bug #66158] Reading a screenrc leads to segfault in 5.0.0
Date: Sun, 1 Sep 2024 07:50:09 -0400 (EDT)

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

                 Summary: Reading a screenrc leads to segfault in 5.0.0
                   Group: GNU Screen
               Submitter: None
               Submitted: Sun 01 Sep 2024 11:50:06 AM UTC
                Category: Crash/Freeze/Infloop
                Severity: 3 - Normal
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                 Release: None
           Fixed Release: None
         Planned Release: None
           Work Required: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Sun 01 Sep 2024 11:50:06 AM UTC By: Anonymous
Description:
Since the update from 4.09.01 to 5.0.0, reading a screenrc leads to a
segfault.
Expected behavior (tested):
```shell
$ screen --version
Screen version 4.09.01 (GNU) 20-Aug-23
$ touch /tmp/screenrc
$ file /tmp/screenrc 
/tmp/screenrc: empty
screen -X source /tmp/screenrc 
$ 
```
All works. Buggy behavior in new version:
```shell
$ 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)
```
Both commands were executed while an open and attached screen (socket).
Originally I had a broken hard status, as in
https://savannah.gnu.org/bugs/?66141, but by trying to narrow down the origin
discovered this potential common cause. I'll mention this issue on the other
bug, too.







    _______________________________________________________

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]