Skip to content

Commit 2d38b5f

Browse files
mjqjjbayer
andauthored
chore: add debug profile + instructions to readme (#4494)
After troubleshooting my failure to debug Relay using VSCode, I found that we had `debug` set to `false` in the dev profile. Added a note to the readme about it in case anyone else runs into the same issue. --------- Co-authored-by: Joris Bayer <[email protected]>
1 parent a098d9e commit 2d38b5f

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

Cargo.toml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,12 @@ resolver = "2"
88
# target folder, but we don't require stack traces in most cases.
99
debug = false
1010

11+
[profile.dev-debug]
12+
# A version of the dev profile with debug information enabled, for e.g. local
13+
# debugging.
14+
inherits = "dev"
15+
debug = true
16+
1117
[profile.release]
1218
# In release, however, we do want full debug information to report
1319
# panic and error stack traces to Sentry.

README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -183,6 +183,12 @@ make format
183183
make lint
184184
```
185185

186+
### Debugging
187+
188+
Developer builds do not include debug information by default. If you want to
189+
attach a debugger to your local Relay, you can use the provided `dev-debug`
190+
profile instead with `cargo run --all-features --profile dev-debug`.
191+
186192
### Python and C-ABI
187193

188194
Potentially, new functionality also needs to be added to the Python package.

0 commit comments

Comments
 (0)