a65e9e5828did not inform `tryEval` that (as far as it's concerned) `state.debug` moved to `state.errors.debug` and changed types. this resulted in the REPL erroneously coming up, that REPL having a non-debug state, and segfaulting after that REPL exited. it's probably good that `state.debug` isn't mutated by `--ignore-try` anymore. Change-Id: I1918e93edacd626452aa423fc2eb825080738835 Fixes:a65e9e5828("libexpr: extract eval error creation into new type") Signed-off-by: Dusk Banks <me@bb010g.com>
563 B
563 B
synopsis, issues, cls, category, credits
| synopsis | issues | cls | category | credits | ||
|---|---|---|---|---|---|---|
| Fix `--debugger --ignore-try` |
|
Fixes |
|
When in debug mode (e.g. from using the --debugger flag), enabling ignore-try once again properly disables debug REPLs within builtins.tryEval calls. Previously, a debug REPL would be started as if ignore-try was disabled, but that REPL wouldn't actually be in debug mode, and upon exiting the REPL the evaluating process would segfault.