Bug 1916854

Summary:	Request for ability to "unset" scope within crash
Product:	Red Hat Enterprise Linux 8	Reporter:	John Pittman <jpittman>
Component:	crash	Assignee:	lijiang
Status:	CLOSED ERRATA	QA Contact:	xiaoying yan <yiyan>
Severity:	medium	Docs Contact:
Priority:	high
Version:	8.2	CC:	ruyang, skurup, xiawu
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	crash-7.3.0-2.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1951401 (view as bug list)		Environment:
Last Closed:	2021-11-09 18:08:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1951401

Description John Pittman 2021-01-15 16:46:24 UTC

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.

Comment 1 John Pittman 2021-01-15 23:12:56 UTC

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

Comment 2 John Pittman 2021-01-18 14:47:33 UTC

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

Comment 3 lijiang 2021-02-22 02:55:33 UTC

The patch has been merged in upstream:

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

Comment 9 errata-xmlrpc 2021-11-09 18:08:37 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 (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