Skip to content

[docs] Improve documentation on LSAN failure symbolication #75451

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 24, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions docs/LSANFailureSymbolication.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,11 +2,12 @@

### Create Ubuntu Container

1. Clone (or pull) swift-docker: https://github.com/swiftlang/swift-docker
2. Build the Ubuntu 18.04 container: `cd swift-ci/master/ubuntu/18.04; docker build .`
3. `docker run -it --cpus <CPUs> --memory <Memory> -v ~/<path to your local sources>:/src-on-host:cached --name lsan-reproducer --cap-add=SYS_PTRACE --security-opt seccomp=unconfined <hash that docker build outputs> bash`
1. Use an x86 machine. The following instructions currently don’t work on arm64. It might be easy to adjust them or not, I have not tried
2. Clone (or pull) swift-docker: https://github.com/swiftlang/swift-docker
3. Build the Ubuntu 22.04 container: `cd swift-ci/master/ubuntu/22.04; docker build .`
4. `docker run -it --cpus <CPUs> --memory <Memory> -v ~/<path to your local sources>:/src-on-host:cached --name lsan-reproducer --cap-add=SYS_PTRACE --security-opt seccomp=unconfined <hash that docker build outputs> bash`
- The `-cap-add` and `-security-opt` arguments are needed to run LLDB inside the Docker container
4. Copy the sources to inside the Docker container: `cp -r /src-on-host/* ~`
5. Copy the sources to inside the Docker container: `cp -r /src-on-host/* ~`
- We need to to this because the build needs a case-sensitive file system and your host machine probably has a case-insensitive file system

Build inside the Container
Expand Down