Crash has some support for per-cpu variables, but it really only works for static variables. My idea is that you should be able to take a per-cpu pointer and see the formatted data. The syntax should allow to specify a CPU or do it for all:

crash&gt; percpu $CPU  <address>
crash&gt; percpu -a  <address>

It should also be usable with static variables:

crash&gt; percpu -a 

Looking for hackers with the skills:

crash coredump

This project is part of:

Hack Week 10

Activity

  • about 11 years ago: ptesarik added keyword "crash" to this project.
  • about 11 years ago: ptesarik added keyword "coredump" to this project.
  • about 11 years ago: ptesarik started this project.
  • about 11 years ago: ptesarik originated this project.

  • Comments

    • ptesarik
      about 11 years ago by ptesarik | Reply

      This is finished. Upstream doesn't like adding new commands, so it may be re-implemented as options to existing commands instead.

    • ptesarik
      about 7 years ago by ptesarik | Reply

      Accepted as address syntax enhancement (denoted with a ':').

    Similar Projects

    Symbol Relations by hli

    Description

    There are tools to build function call graphs based on parsing source code, for example, cscope.

    This project aims to achieve a similar goal by directly parsing the disasembly (i.e. objdump) of a compiled binary. The assembly code is what the CPU sees, therefore more "direct". This may be useful in certain scenarios, such as gdb/crash debugging.

    Detailed description and Demos can be found in the README file:

    Supports x86 for now (because my customers only use x86 machines), but support for other architectures can be added easily.

    Tested with python3.6

    Goals

    Any comments are welcome.

    Resources

    https://github.com/lhb-cafe/SymbolRelations

    symrellib.py: mplements the symbol relation graph and the disassembly parser

    symrel_tracer*.py: implements tracing (-t option)

    symrel.py: "cli parser"