-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.
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
Useful stacktraces with gc:orc #19491
Comments
This is supposed to work. Can you provide a test case? |
There you go, wasn't hard. It would be probably a good idea to add a unit test for this for the future. test.nimproc foo() =
let x = -1
discard x.Natural
proc main() =
foo()
main() gc:refc
gc:arc
gc:orc
|
Duplicate of #19078 It works on devel, 1.6.2 |
Great to hear, but I can't use 1.6.2 yet due to the FFI bug... I'll just wait for the final 1.6.4. |
Here is the release of 1.6.4 https://github.com/nim-lang/Nim/releases/tag/v1.6.4 feel free to reopen the issue if it doesn't work for you. |
Just confirming that the stacktraces work as expected in 1.6.4 with all different GCs. |
Nim 1.6.0 doesn't seem to provide proper stacktraces when certain types of runtime errors are encountered (seems like Defects are behaving like this).
Observe the difference between what's printed out when using
gc:orc
vsgc:refc
.The lack of proper stacktraces is a big deal not only during development (not everybody is happy to use a debugger all the time), but especially for production applications where you want to collect crash logs with useful stacktraces from users who ran into problems. Therefore, using ORC/ARC is not an option for me until we get proper stacktraces like with the default
refc
implementation.gc:orc
gc:refc
The text was updated successfully, but these errors were encountered: