Skip to content
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.

Sign up for GitHub

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

fix readme #13

Merged
merged 1 commit into from
Mar 14, 2021
Merged

fix readme #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
20 changes: 4 additions & 16 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"`.

Expand Down