Skip to content
Open-Source Registry

cargo / cargo-debuggable

cargo-debuggable 0.1.1

processes
197
operations
2.8K
packages
10
compiler runs
4
connections
1
job time
14s
capture
54 KB
records
5.5K
bytes / record
9.9

Sets up GDB, LLDB and VS Code (CodeLLDB) for the `debuggable` crate, and checks binaries

clean

Build behaviournot recorded for this run

7 downloads · source · cargo

cargo-subcommand debugger gdb lldb vscode

Release 0.1.1 run 8c852c1f-1f67-4dd6-b7d8-1c70065c8b44 · built 2026-10-07

Artifact

binary · retained · product
1
ChecksDetections
Build behavior
✓ Network activity—
✓ Sensitive data access and transfer—
✓ Cross-process access—
✓ Build file changes—
✓ Build script activity—
✓ Data flow analysis—
✓ Filesystem writes—
✓ Context collection—
Supply chain
✓ Known vulnerabilities—
✓ Build-time dependency advisories—
✓ Dependency advisories—
✓ Declared and observed dependencies—
✓ Dependency and toolchain versions—
Pipeline
✓ Pipeline coverage—

Detections

0

No detections

No abnormal activity detected across 2.8K flows.

Network

1 peers
  • static.crates.io:8080
    cargo (debuggable) via crates.io · build-test
    allowed

Raw data

capture
54 KB
records
5,496
bytes per record
9.9

Loading a sample of the capture

Want to see more? E-mail us at hello@bitbison.io about your use case.

Dependencies

10 packages, 0 with a build script that ran, 0 doing more than compiling
PackageVersionUsageBuild behaviour
fallible-iterator0.3.0feature_gated
gimli direct0.32.3linked
ld-linux-x86-64.so.2linked
libc.so.6linked
libgcc_s.so.1linked
libm.so.6linked
libmvec.so.1linked
memchr2.8.3linked
object direct0.39.1linked
stable_deref_trait1.2.1feature_gated

1 of 1 jobs captured: build-test success · Generated 2026-10-07 · tarp 0.1.0+20261007022833-g16cc1581f632 · run 8c852c1f-1f67-4dd6-b7d8-1c70065c8b44