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.

Description of problem:

Request for ability to "unset" scope within crash

Version-Release number of selected component (if applicable):

crash-7.2.8-7.el8
(issue looks to be present upstream as well)

How reproducible:

Every time

Steps to Reproduce:

crash64> set scope
scope: 0 (not set)

crash64> set scope schedule
scope: ffffffffbb1c12a0 (schedule)

crash64> set scope 0
set: invalid text address: 0

Actual results:

Once scope is set, we can only set to a different symbol.
We can not unset it completely.

Expected results:

There should be the ability to completely unset scope.  The reason for
this is that when running automated scripts against vmcores, from script
to script there is a need to clear the scope sets.  Currently there is no
way to do this as gdb_set_crash_scope() will return an error if is_kernel_text()
returns 0.

Request for ability to un-set submitted upstream at https://github.com/crash-utility/crash/pull/75

Pull requests not being accepted via github, so patch sent to https://www.redhat.com/archives/crash-utility/2021-January/msg00024.html instead.

The patch has been merged in upstream:

e4c1617e17eb ("set: add ability to un-set scope")

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 (crash 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/RHBA-2021:4199