> Hmm, looks like opt:speed might interfere with debugging can you show such example (ideally reduced) ?
I could see how that would be the case with `-d:nimStackTraceOverride --import:libbacktrace --debugger:native` (see also: `--passc:"-fno-omit-frame-pointer -fno-optimize-sibling-calls"` refs <https://github.com/status-im/nim-libbacktrace/pull/10)>, but how would it affect `--stacktrace:on`, which uses instrumentation that shouldn't be affected by backend optimization options ? (see also <https://github.com/nim-lang/Nim/pull/13582> which relates to this topic)
