Bug 114638
Summary: | binutils (nm/objdump) manpage is missing information | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Dag Wieers <dag> |
Component: | binutils | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 19:30:42 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dag Wieers
2004-01-30 15:11:33 UTC
Why should nm man page document symbol types displayed by objdump? Well, how it is now is that the objdump manpage refers to the nm page for a list of symbols. This list is incomplete, so either the list is copied to the manpage of objdump or it is extend in the nm manpage. I'm not arguing where it should go, I'm just arguing to add a full list as I've looked in the code of objdump and couldn't find all the symbols myself. And it is valuable information that should go in the manpage. manpages should at least explain the output ;-) Thanks for your work. This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |