Skip to content

Use kdumpfile module address space constants#1

Merged
jeffmahoney merged 1 commit intocrash-python:masterfrom
ptesarik:master
Apr 24, 2016
Merged

Use kdumpfile module address space constants#1
jeffmahoney merged 1 commit intocrash-python:masterfrom
ptesarik:master

Conversation

@ptesarik
Copy link
Copy Markdown
Contributor

Commit ee04e262c9eb70c7272859bb0985d34b55b09aba in libkdumpfile broke
the kdump target, as it changes address space constants to module
constants.

Signed-off-by: Petr Tesarik [email protected]

Commit ee04e262c9eb70c7272859bb0985d34b55b09aba in libkdumpfile broke
the kdump target, as it changes address space constants to module
constants.

Signed-off-by: Petr Tesarik <[email protected]>
@jeffmahoney jeffmahoney merged commit cef6cdf into crash-python:master Apr 24, 2016
jeffmahoney pushed a commit that referenced this pull request Jul 12, 2018
Without the patch, the backtrace displays the "cannot resolve stack
trace" warning, dumps the backtrace, and then the text symbols:

  crash> bt
  PID: 0      TASK: f0962180  CPU: 6   COMMAND: "swapper/6"
  bt: cannot resolve stack trace:
   #0 [f095ff1c] __schedule at c0b6ef8d
   #1 [f095ff58] schedule at c0b6f4a9
   #2 [f095ff64] schedule_preempt_disabled at c0b6f728
   #3 [f095ff6c] cpu_startup_entry at c04b0310
   #4 [f095ff94] start_secondary at c04468c0
  bt: text symbols on stack:
      [f095ff1c] __schedule at c0b6ef8d
      [f095ff58] schedule at c0b6f4ae
      [f095ff64] schedule_preempt_disabled at c0b6f72d
      [f095ff6c] cpu_startup_entry at c04b0315
      [f095ff94] start_secondary at c04468c5
  crash>

The backtrace shown is actually correct.
([email protected])
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants