Bug 1715746 - Tmux core killed by SIGEGV
Summary: Tmux core killed by SIGEGV
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tmux
Version: 7.8
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: David Cantrell
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-31 07:14 UTC by Matteo
Modified: 2021-03-15 07:36 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-15 07:36:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matteo 2019-05-31 07:14:08 UTC
Description of problem:

tmux crashes without notice.
By inspecting the /var/log/messages I found:

```
May 31 08:50:26 h abrt-hook-ccpp: Process 24541 (tmux) of user 1000 killed by SIGSEGV - dumping core
May 31 08:50:26 h abrt-hook-ccpp: Failed to create core_backtrace: dwfl_getthread_frames failed: No DWARF information found
May 31 08:50:26 h systemd-logind: Removed session 6.
May 31 08:50:26 h abrt-server: Generating core_backtrace
May 31 08:50:26 h dbus[10911]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)
May 31 08:50:26 h dbus[10911]: [system] Successfully activated service 'org.freedesktop.problems'
May 31 08:50:26 h abrt-server: Email address of sender was not specified. Would you like to do so now? If not, 'user@localhost' is to be used [y/N] 
May 31 08:50:26 h abrt-server: Email address of receiver was not specified. Would you like to do so now? If not, 'root@localhost' is to be used [y/N] 
May 31 08:50:26 h abrt-server: Sending an email...
May 31 08:50:26 h abrt-server: Sending a notification email to: root@localhost
May 31 08:50:27 h abrt-server: Email was sent to: root@localhost
```

How reproducible:

It crashes, just leave it open.
I attached a log.

Actual results:

It crashes

Expected results:

It should not

Additional info:

Comment 4 RHEL Program Management 2021-03-15 07:36:30 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.