status-im
/
nim-libbacktrace
mirror of https://github.com/status-im/nim-libbacktrace.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

fix readme (#13)

This commit is contained in:
Timothee Cour 2021-03-14 12:37:41 -07:00 committed by GitHub
parent f0bbe7eb6b
commit 829a65ca3d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@ -59,25 +59,13 @@ We need debugging symbols in the binary and we can do without Nim's bloated and
slow stack trace implementation:
```bash
nim c -f --debugger:native --stacktrace:off bttest.nim
```
If you're unfortunate enough to need this on macOS, [there's an extra
step](https://github.com/nim-lang/Nim/issues/12735) for creating debugging
symbols:
```bash
dsymutil bttest
```
Now you can run it:
```bash
./bttest
# `-f` needed if you've changed nim-libbacktrace
# just use `c` if you're just compiling
nim r --debugger:native --stacktrace:off bttest.nim
```
When the C compiler inlines some functions, or does tail-call optimisation -
usually with `-d:release` - your stack trace might be incomplete.
usually with `-d:release` or `-d:danger` - your stack trace might be incomplete.
If that's a problem, you can use `--passC:"-fno-inline -fno-optimize-sibling-calls"`.