Skip to content

Include threads into task list.#3

Merged
jeffmahoney merged 1 commit intocrash-python:crash-wipfrom
alesax:alno-threads
Jun 29, 2016
Merged

Include threads into task list.#3
jeffmahoney merged 1 commit intocrash-python:crash-wipfrom
alesax:alno-threads

Conversation

@alesax
Copy link
Copy Markdown

@alesax alesax commented Jun 29, 2016

Threads are currently not included within the list of tasks.

This stupid patch does that, by walking the thread_group of each task.

@jeffmahoney jeffmahoney merged commit 8ed8768 into crash-python:crash-wip Jun 29, 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