Red Hat Bugzilla – Bug 834257
sym comand should print '0x' prefix before printing the actual value
Last modified: 2013-03-03 20:35:17 EST
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
megatron$ rpm -qf `which crash`
Steps to Reproduce:
1. sym schedule
crash> sym schedule
ffffffff800623d0 (T) schedule ../debug/kernel-2.6.18/linux-2.6.18-308.el5.x86_64/kernel/sched.c: 3520
crash> sym schedule
0xffffffff800623d0 (T) schedule ../debug/kernel-2.6.18/linux-2.6.18-308.el5.x86_64/kernel/sched.c: 3520
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
> 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 email@example.com 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
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.
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.