Enhance kdumpid
an invention by ptesarik
Updated over 5 years ago. 1 hackers ♥️.

The kdumpid tool can be used to determine the kernel version from a crash dump. Some useful features are missing:

  • support for new compression methods (lzo, snappy)
  • support for new architectures (ppc64le)
  • for Xen dumps, include the hypervisor version in the output

Status after Hackweek 11

The kdumpid application has switched to libkdumpfile (see also the gdb-kdump Hackweek Project), which adds support for lzo and snappy. Partial support of ppc64le has been added, too. Xen hypervisor version is detected and printed.

Looking for hackers with the skills:

c crash coredump

This project is part of:

Hack Week 11

Activity

  • about 10 years ago: sleep_walker liked this project.
  • about 10 years ago: ptesarik added keyword "c" to this project.
  • about 10 years ago: ptesarik added keyword "crash" to this project.
  • about 10 years ago: ptesarik added keyword "coredump" to this project.
  • about 10 years ago: ptesarik started this project.
  • about 10 years ago: ptesarik originated this project.


    • Comments

    Be the first to comment!

    Similar Projects

    Add a machine-readable output to dmidecode by jdelvare

    Description

    There have been repeated requests for a machine-friendly dmidecode output over the last decade. During Hack Week 19, 5 years ago, I prepared the code to support alternative output formats, but didn't have the time to go further. Last year, Jiri Hnidek from Red Hat Linux posted a proof-of-concept implementation to add JSON output support. This is a fairly large pull request which needs to be carefully reviewed and tested.

    Goals

    Review Jiri's work and provide constructive feedback. Merge the code if acceptable. Evaluate the costs and benefits of using a library such as json-c.

    FizzBuzz OS by mssola

    Project Description

    FizzBuzz OS (or just fbos) is an idea I've had in order to better grasp the fundamentals of the low level of a RISC-V machine. In practice, I'd like to build a small Operating System kernel that is able to launch three processes: one that simply prints "Fizz", another that prints "Buzz", and the third which prints "FizzBuzz". These processes are unaware of each other and it's up to the kernel to schedule them by using the timer interrupts as given on openSBI (fizz on % 3 seconds, buzz on % 5 seconds, and fizzbuzz on % 15 seconds).

    This kernel provides just one system call, write, which allows any program to pass the string to be written into stdout.

    This project is free software and you can find it here.

    Goal for this Hackweek

    • Better understand the RISC-V SBI interface.
    • Better understand RISC-V in privileged mode.
    • Have fun.

    Resources

    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"