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.
Bug 1445649 - crash: running disassemble cmd returns error: "gdb: gdb request failed"
Summary: crash: running disassemble cmd returns error: "gdb: gdb request failed"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: crash
Version: 7.4
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Dave Anderson
QA Contact: Emma Wu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-26 08:45 UTC by Emma Wu
Modified: 2019-02-19 21:41 UTC (History)
2 users (show)

Fixed In Version: crash-7.1.9-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 22:04:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2019 0 normal SHIPPED_LIVE crash bug fix and enhancement update 2017-08-01 19:31:13 UTC

Comment 2 Dave Anderson 2017-04-26 13:26:44 UTC 
This is a KASLR issue.  Except for the patched gdb minimal_symbols, the embedded
gdb still operates under the assumption that the (non-relocated) text locations
in the vmlinux file are correct.   

I never use the gdb "disassemble" command, and so I never noticed this until
now.  The crash "dis" command is always preferable to use instead of the 
native gdb command.  It's possible that the gdb disassemble command may have
to be prohibited with KASLR kernels.
Comment 3 Dave Anderson 2017-05-01 19:47:53 UTC 
I tinkered with this for a couple of days, and failed to come up with a
reasonable solution in the gdb code.  And given that the crash "dis" command
is the preferred manner of text disassembly, I'm not going to pursue it
any further -- except to clarify the error message as shown in this
example:

  crash> disassemble sys_read
  crash: the gdb "disassemble" command is prohibited because the kernel text
         was relocated by KASLR; use the crash "dis" command instead.
  crash>

A patch for the new error message has been pushed upstream:

https://github.com/crash-utility/crash/commit/c85a70ba752ac31e729a753a03b836dc5591714b

  The native gdb "disassemble" command fails if the kernel has been
  compiled with CONFIG_RANDOMIZE_BASE because the embedded gdb module
  still operates under the assumption that the (non-relocated) text
  locations in the vmlinux file are correct.  The error message that
  is issued is somewhat confusing, indicating "No function contains
  specified address".  This patch simply clarifies the error message
  to indicate "crash: the gdb "disassemble" command is prohibited
  because the kernel text was relocated by KASLR; use the crash "dis"
  command instead."
  (anderson)

I'm not sure whether I should just close this BZ as CANTFIX, or to
give it a devel_ack+ for rhel-7.4.  

Do you consider this worthy of an errata respin?
Comment 8 errata-xmlrpc 2017-08-01 22:04:38 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, 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-2017:2019
Note You need to log in before you can comment on or make changes to this bug.