ziglang/zig

Fork 778

Code Issues 711 Pull requests 299 Activity Actions 24

debug-prefix-map support #31001

New issue

Open

opened 2026年01月25日 20:57:59 +01:00 by steeve · 4 comments

steeve commented

2026年01月25日 20:57:59 +01:00

Contributor

Copy link

Hello Zig community,

So it's not a bug but rather a request/feature proposal for the zig cli.

GCC and Clang support the -fdebug-prefix-map flag to prevent absolute path from ending up in the binary (usually DWARF).

Zig doesn't have such a flag, so absolute paths "leak" into the binary, preventing hermetic builds.

I am open to adding the functionality if there is support.

Thank you!

PS: I did not mean zig cc but zig itself

Hello Zig community, So it's not a bug but rather a request/feature proposal for the `zig` cli. GCC and Clang support the `-fdebug-prefix-map` flag to prevent absolute path from ending up in the binary (usually DWARF). Zig doesn't have such a flag, so absolute paths "leak" into the binary, preventing hermetic builds. I am open to adding the functionality if there is support. Thank you! PS: I did not mean `zig cc` but `zig` itself

👍 1 👀 2 ❤️ 2

alexrp added the

enhancement

frontend

debug info

labels

2026年01月25日 21:43:58 +01:00

nicolaschavez commented

2026年03月22日 03:09:20 +01:00

Copy link

+1, will just mention one more use case: this makes it possible to debug Zig compiled to WASM with DWARF in Chrome with the C/C++ DevTools extension, without hardcoding the file:// path that gets baked in by default; whereas in my use case, I am serving the source files from the same (dev) server that the WASM+DWARF binary is serving from (so, I'd like to use a relative debug prefix). For now, I have to use C23 instead of Zig as a result.

cerisier commented

2026年06月02日 19:03:08 +02:00

Contributor

Copy link

I am willing to work on supporting this while I'm on improving all sort of debug stuff like #31821 or #31821

Tho I would love to get maintainers word on it and what would be a good first milestone that can land.

I am willing to work on supporting this while I'm on improving all sort of debug stuff like #31821 or #31821 Tho I would love to get maintainers word on it and what would be a good first milestone that can land.

cerisier commented

2026年06月03日 17:31:32 +02:00

Contributor

Copy link

Thinking of this a bit more, preventing absolute paths to end up in the binary would require more than -fdebug-prefix-map.
clang offers a whole family of flags like:

file/debug-compilation-dir
file/debug/macro/coverage-prefix-map
and -ffile-reproducible to use the target path separator in file paths

I think we should get a clear guideilne on wether Zig wants similar knobs and how they would affect various zig features.
I'm thinking stuff like @src() and std.builtin.SourceLocation

I think all of these are quite similar in the implementation so worth knowing if all make sense at once and what the API should be if not exactly that of clang.

Would love to get maintainers insights on this.

Thinking of this a bit more, preventing absolute paths to end up in the binary would require more than -fdebug-prefix-map. clang offers a whole family of flags like: - file/debug-compilation-dir - file/debug/macro/coverage-prefix-map - and -ffile-reproducible to use the target path separator in file paths I think we should get a clear guideilne on wether Zig wants similar knobs and how they would affect various zig features. I'm thinking stuff like @src() and std.builtin.SourceLocation I think all of these are quite similar in the implementation so worth knowing if all make sense at once and what the API should be if not exactly that of clang. Would love to get maintainers insights on this.

cerisier commented

2026年06月03日 23:45:14 +02:00

Contributor

Copy link

cc @alexrp maybe it makes sense to make a different issue about this ?

No Branch/Tag specified

Branches Tags

master

elfv2

spork8

restricted

0.16.x

panic-rewrite

parking-futex-lockfree

windows-Io-cleanup

Io-watch

ParseCommandLineOptions

windows-async-files

poll-ring

debug-file-leaks-differently

debug-file-leaks

ProcessPrng

elfv2-dyn

jobserver

threadtheft

io-threaded-no-queue

0.15.x

Io.net

comptime-allocator

restricted-function-pointers

cli

wasm-linker-writer

wrangle-writer-buffering

sha1-stream

async-await-demo

fixes

0.14.x

ast-node-methods

macos-debug-info

make-vs-configure

fuzz-macos

sans-aro

ArrayList-reserve

incr-bug

llvm-ir-nosanitize-metadata

ci-tarballs

ci-scripts

threadpool

0.12.x

new-pkg-hash

json-diagnostics

more-doctests

rework-comptime-mutation

0.11.x

ci-perf-comment

stage2-async

0.10.x

autofix

0.9.x

aro

hcs

0.8.x

0.7.x

Labels

Clear labels

This proposal is planned.

The web application for interactive documentation and generation of its assets.

backend/c

The C backend outputs C source code.

backend/llvm

The LLVM backend outputs an LLVM bitcode module.

backend/self-hosted

The self-hosted backends produce machine code directly.

binutils

Zig's included binary utilities: zig ar, zig dlltool, zig lib, zig ranlib, zig objcopy, and zig rc.

breaking

Implementing this issue could cause existing code to no longer compile or have different behavior.

build system

The Zig build system - zig build, std.Build, the build runner, and package management.

debug info

docs

An issue with documentation, e.g. the language reference or standard library doc comments.

error message

This issue points out an error message that is unhelpful and should be improved.

frontend

Tokenization, parsing, AstGen, ZonGen, Sema, Legalize, and Liveness.

fuzzing

incremental

Reuse of internal compiler state for faster compilation.

lib/c

This issue relates to Zig's libc implementation and/or vendored libcs.

lib/compiler-rt

This issue relates to Zig's compiler-rt library.

lib/cxx

This issue relates to Zig's vendored libc++ and/or libc++abi.

lib/std

This issue relates to Zig's standard library.

lib/tsan

This issue relates to Zig's vendored libtsan.

lib/ubsan-rt

This issue relates to Zig's ubsan-rt library.

lib/unwind

This issue relates to Zig's vendored libunwind.

linking

Zig's integrated object file and incremental linker.

miscompilation

The compiler reports success but produces semantically incorrect code.

This issue suggests language modifications. If it also has the "accepted" label then it is planned.

release notes

This issue or pull request should be mentioned in the release notes.

testing

This issue is related to testing the compiler, standard library, or other parts of Zig.

zig cc

Zig as a drop-in C-family compiler.

zig fmt

The Zig source code formatter.

zig reduce

The Zig source code reduction tool.

bounty

https://ziglang.org/news/announcing-donor-bounties

bug

Observed behavior contradicts documented or intended behavior.

contributor-friendly

This issue is limited in scope and/or knowledge of project internals.

downstream

An issue with a third-party project that uses this project.

enhancement

Solving this issue will likely involve adding new logic or components to the codebase.

infra

optimization

A task to improve performance and/or resource usage.

question

No questions on the issue tracker; use a community space instead.

regression

Something that used to work in a previous version stopped working

upstream

An issue with a third-party project that this project uses.

use case

Describes a real use case that is difficult or impossible, but does not propose a solution.

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

3 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

ziglang/zig#31001

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?