iovisor/bcc

Application stack trace on oomkill.

Open

#3,654 opened on Oct 11, 2021

View on GitHub
 (7 comments) (0 reactions) (0 assignees)C (22,409 stars) (4,051 forks)batch import
enhancementgood first issuenew option

Description

Is it possible to get an application level stack trace on oomkill? Are there any examples of how I might write a script to do something like that?

Contributor guide

Tech stack
c
Domain
observability
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Linux OOM killerBPFBCC
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate existing BCC tools for tracing OOM events (e.g., oomkill.py) and check how stack traces are captured. Look at the BPF program structure in the examples directory to understand how to attach to tracepoints or kprobes related to oom kill. Examine the BCC documentation and source code for helper functions to retrieve user space stack traces.
Application stack trace on oomkill. · iovisor/bcc#3654 | Good First Issue