Upstream software project

uftrace

A function call graph tracer for C, C++, Rust and Python programs

About uftrace

A function call graph tracer for C, C++, Rust and Python programs

This project links 3 native package records across 3 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

uftrace repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.uftrace: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
uftrace
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
debian-12, debian-13, opensuse-tumbleweed
License expression
GPL-2.0-only
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

uftrace is a function call graph tracer for C, C++, Rust and Python programs. It hooks into the entry and exit of each function, recording timestamps as well as the function's arguments and return values. uftrace is capable of tracing both user and kernel functions, as well as library functions and system events providing an integrated execution flow in a single timeline. Initially, uftrace only supported function tracing with compiler support. However, it now allows users to trace function calls without recompilation by analyzing instructions in each function prologue and dynamically and selectively patching those instructions. Users can also write and run scripts for each function entry and exit using python/luajit APIs to create custom tools for their specific purposes. uftrace offers various filters to reduce the amount of trace data and provides visualization using Chrome trace viewer and flame graph or call-graph diagrams for graphviz and mermaid, allowing for a big picture view of the execution flow. It was heavily inspired by the ftrace framework of the Linux kernel and the name uftrace stems from the combination of user and ftrace.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. Package uftrace

    bookworm (Debian 12 (Bookworm)) (utils): Traces and analyzes execution of programs written in C/C++

    0.13-1: amd64 arm64

Debian 13 (Trixie)

  1. Package uftrace

    trixie (Debian 13 (Trixie)) (utils): Traces and analyzes execution of programs written in C/C++

    0.17-1: amd64 arm64

openSUSE Tumbleweed

  1. Package uftrace

    tumbleweed (openSUSE Tumbleweed) (Development/Tools/Debuggers): A function call graph tracer for C, C++, Rust and Python programs

    0.19-1.4: x86_64

    Source: uftrace

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.