Bazel: debug info embeds absolute paths into the sandbox

Open
#1,129 0 comments 0 reactions 1 assignee View on GitHub

@walkingeyerobot is already working on this.

Since Nov 9, 2022.

Assessment

This issue has not been assessed yet.

Description

If you build with -g or -gseparate-dwarf, the generated symbols will contain absolute paths into Bazel's sandbox directory. Those directories don't exist beyond the lifetime of an individual compile action, so the resulting debug symbols aren't useful. For example, you won't be able to debug using Chrome Developer Tools.

The way that Bazel toolchains usually address this is one of the following:

Dominant language
Python
Stars
3.7k
Forks
822
Avg merge
2d 6h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from emscripten-core/emsdk

All issues in emscripten-core/emsdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.