Bug 834257

Summary:	sym comand should print '0x' prefix before printing the actual value
Product:	Red Hat Enterprise Linux 6	Reporter:	Stanislav Kozina <skozina>
Component:	crash	Assignee:	Dave Anderson <anderson>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	mhomolov, plyons
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-16 15:41:46 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:

Description Stanislav Kozina 2012-06-21 11:20:26 UTC

Description of problem:

sym command should print 0x prefix before the hex address, so the output could be directly passed to px command if neccessary.

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

# rpm -qf /usr/bin/crash
crash-5.1.8-1.el6.x86_64
megatron$ rpm -qf `which crash`
crash-6.0.5-0.x86_64

How reproducible:

Always

Steps to Reproduce:
1. sym schedule
2.
3.
  
Actual results:

crash> sym schedule
ffffffff800623d0 (T) schedule ../debug/kernel-2.6.18/linux-2.6.18-308.el5.x86_64/kernel/sched.c: 3520

Expected results:

crash> sym schedule
0xffffffff800623d0 (T) schedule ../debug/kernel-2.6.18/linux-2.6.18-308.el5.x86_64/kernel/sched.c: 3520

Additional info:

Comment 1 Dave Anderson 2012-06-21 13:17:25 UTC

Sorry, no, that's not going to happen.  A foundational tenet of the
crash utility is the avoidance of the 0x whenever possible, both for user
input and command output.

Now, I would consider adding an option to the "sym" command that would pre-pend
the 0x.

Comment 3 Dave Anderson 2012-06-21 15:12:19 UTC

> Is 123456 Dec/Hex/Oct ?

Can you give me an example where there's a question of what a number is?

> Does crash utility team have any strategy, how to handle such cases?

There's no "crash utility team" -- there's me, plus an active community
that I lead on the crash-utility mailing list.  Patches are
posted there regularly and other discussions held, but I am the gate-keeper
since I wrote the thing from scratch many years ago.  I typically release
a new upstream version once-a-month.  I do have some architecture 
sub-maintainers for ARM, S390X and PPC64, who handle some of the more
machine-specific stuff.

Comment 4 RHEL Program Management 2012-07-10 06:59:47 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 5 RHEL Program Management 2012-07-10 23:10:33 UTC

This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.