RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1856178 - memstrack: q cann't quit from memstrack TUI
Summary: memstrack: q cann't quit from memstrack TUI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: memstrack
Version: 8.3
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Kairui Song
QA Contact: Li Wang
URL:
Whiteboard:
Depends On:
Blocks: 1814488
TreeView+ depends on / blocked
 
Reported: 2020-07-13 05:28 UTC by Li Wang
Modified: 2020-11-04 01:55 UTC (History)
1 user (show)

Fixed In Version: memstrack-0.1.8-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 01:54:49 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:4516 0 None None None 2020-11-04 01:54:59 UTC

Description Li Wang 2020-07-13 05:28:06 UTC 
Description of problem:

memstrack-0.1.8-1.el8.x86_64

After entering 'q' we can't quit from TUI.
Comment 1 Li Wang 2020-07-13 05:35:27 UTC 
If we adding back the m_exit(0), it works fine.

diff --git a/src/tui.c b/src/tui.c
index a84fe74..726e729 100644
--- a/src/tui.c
+++ b/src/tui.c
@@ -340,7 +340,7 @@ void tui_loop(void) {
                        case 'q':
                        case 'Q':
                                endwin();
-                               /// m_exit(0);
+                               m_exit(0);
                                return;
 
                        case 'm':
Comment 2 Kairui Song 2020-07-13 05:56:31 UTC 
(In reply to Li Wang from comment #1)
> If we adding back the m_exit(0), it works fine.
> 
> diff --git a/src/tui.c b/src/tui.c
> index a84fe74..726e729 100644
> --- a/src/tui.c
> +++ b/src/tui.c
> @@ -340,7 +340,7 @@ void tui_loop(void) {
>                         case 'q':
>                         case 'Q':
>                                 endwin();
> -                               /// m_exit(0);
> +                               m_exit(0);
>                                 return;
>  
>                         case 'm':

Thanks, I guess I commented that out by accident, let me fix it.
Comment 8 errata-xmlrpc 2020-11-04 01:54:49 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (memstrack bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:4516
Note You need to log in before you can comment on or make changes to this bug.