screen-devel
[Top][All Lists]
Advanced

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

[screen-devel] [bug #58259] Memory corruption by terminfo


From: Victor Dmitriev
Subject: [screen-devel] [bug #58259] Memory corruption by terminfo
Date: Mon, 27 Apr 2020 11:14:14 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0

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

                 Summary: Memory corruption by terminfo
                 Project: GNU Screen
            Submitted by: mrwitek
            Submitted on: Mon 27 Apr 2020 03:14:12 PM UTC
                Category: Crash/Freeze/Infloop
                Severity: 3 - Normal
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
                 Release: 4.99.0
         Discussion Lock: Any
           Fixed Release: None
         Planned Release: None
           Work Required: None

    _______________________________________________________

Details:

In version 4.8.0 screen can corrupt memory when reading terminfo/termcap
files.

I use st terminal <https://st.suckless.org/> with environment variable
TERM=st-256color. If I have compiled st.info (with warnings) from the source
with

tic -o "$HOME/.terminfo" st.info

trying to start screen results in one process becoming a zombie and another
process blocking terminal until I press Ctrl+\.

If I have compiled st.info as recommended in st FAQ
<https://git.suckless.org/st/plain/FAQ> with

tic -o "$HOME/.terminfo" -x st.info

trying to reattach to screen session results in an infinite loop in
_nc_find_type_entry in libncursesw.so.6 (bug #58132)

The problem is not present in version 4.7.0.
Workaround: add " -DTERMCAP_BUFSIZE=2048" to CPPFLAGS environment variable and
reconfigure/rebuild. In that case problem is no longer present.

P.S. bugtracker misses 4.8.0 entry in the release field.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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