diff options
author | Andreas Rumpf <rumpf_a@web.de> | 2020-09-22 13:03:24 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-09-22 13:03:24 +0200 |
commit | 1fae66e4df8cc43b4ec8ab97fff96282ef234f2e (patch) | |
tree | 71fb01887cfba648f48e001626d1db7d9de36a1f /tests | |
parent | d67c5cb75171fcbf1ca9078452e8fcbe36fc79bc (diff) | |
download | Nim-1fae66e4df8cc43b4ec8ab97fff96282ef234f2e.tar.gz |
better nativestacktrace support; refs #15284; backport [1.2] (#15384)
* nimStackTraceOverride: enable stack traces in exceptions This is a two-step stack trace collection scheme, because re-raised exceptions will collect multiple stack traces but use them rarely, when printing info about an uncaught exception, so it makes sense to only do the cheap stack unwinding all the time and the relatively expensive debugging information collection on-demand. `asyncfutures` implements its own `$` proc for printing `seq[StackTraceEntry]`, so we have to add the debugging info there, just like we do for the private `$` proc in `system/excpt`. * cleaned up PR #15284 Co-authored-by: Ștefan Talpalaru <stefantalpalaru@yahoo.com>
Diffstat (limited to 'tests')
-rw-r--r-- | tests/system/tnim_stacktrace_override.nim | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/tests/system/tnim_stacktrace_override.nim b/tests/system/tnim_stacktrace_override.nim new file mode 100644 index 000000000..c75da9d9b --- /dev/null +++ b/tests/system/tnim_stacktrace_override.nim @@ -0,0 +1,18 @@ +discard """ + cmd: "nim c -d:nimStacktraceOverride $file" + output: '''begin +Traceback (most recent call last, using override) +Error: unhandled exception: stack trace produced [ValueError] +''' + exitcode: 1 +""" + +import asyncfutures + +proc main = + echo "begin" + if true: + raise newException(ValueError, "stack trace produced") + echo "unreachable" + +main() |