Upstream software project

debugbreak

Breakpoint injector for C/C++ code

About debugbreak

Breakpoint injector for C/C++ code

This project links 10 native package records across 7 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

debugbreak 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; Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 15.6: 2 package records; openSUSE Leap 16.0: 2 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.debugbreak: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 recordsopenSUSE Leap 15.62 recordsopenSUSE Leap 16.02 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
debugbreak
Publisher
Not authoritatively mapped
Native package records
10
Operating systems
debian-12, debian-13, fedora-43, fedora-44, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
BSD-2-Clause
Source repository
Open source repository

Source-reported description

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

debugbreak.h allows you to put breakpoints in your C/C++ code with a call to debug_break(). • Include one header file and insert calls to debug_break() in the code where you wish to break into the debugger. • Supports GCC, Clang and MSVC. • Works well on ARM, AArch64, i686, x86-64, POWER and has a fallback code path for other architectures. • Works like the DebugBreak() function provided by Windows and QNX.

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 debugbreak

    bookworm (Debian 12 (Bookworm)) (devel): Put breakpoints in C/C++ code

    1.0-1: amd64 arm64

Debian 13 (Trixie)

  1. Package debugbreak

    trixie (Debian 13 (Trixie)) (devel): Put breakpoints in C/C++ code

    1.0-1: amd64 arm64

Fedora 43

  1. Package debugbreak-devel

    43 (Fedora 43) (Unspecified): Break into the debugger programmatically

    1.0-22.fc43: noarch

    Source: debugbreak

Fedora 44

  1. Package debugbreak-devel

    44 (Fedora 44) (Unspecified): Break into the debugger programmatically

    1.0-25.fc44: noarch

    Source: debugbreak

openSUSE Leap 15.6

  1. Package debugbreak

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Breakpoint injector for C/C++ code

    1.0~git.20210702-bp156.2.1: noarch

    Source: debugbreak

  2. Package debugbreak-devel

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Development files for debugbreak

    1.0~git.20210702-bp156.2.1: noarch

    Source: debugbreak

openSUSE Leap 16.0

  1. Package debugbreak

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Breakpoint injector for C/C++ code

    1.0~git.20210702-bp160.1.10: noarch

    Source: debugbreak

  2. Package debugbreak-devel

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Development files for debugbreak

    1.0~git.20210702-bp160.1.10: noarch

    Source: debugbreak

openSUSE Tumbleweed

  1. Package debugbreak

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Breakpoint injector for C/C++ code

    1.0~git.20210702-1.8: noarch

    Source: debugbreak

  2. Package debugbreak-devel

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Development files for debugbreak

    1.0~git.20210702-1.8: noarch

    Source: debugbreak

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.