-
-
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
line number missing from stacktrace #14444
Comments
templates don't stacktrace properly in general, they eat one line. |
that's an unrelated issue, the line number is missing even without templates, eg: when true: # example i gave in https://forum.nim-lang.org/t/6355#39311
echo "ok0"
var i = ""
var u0 = 12
echo "ok1" ## <- line number points to here
const u1 = 12
var u2 = 12
i[10] = 'j'
echo i For templates, I think we can also improve things (see timotheecour#259); the idea is to add nimfr_ + popFrame + goto to templates so that they appear as regular procs as far as stacktraces are concerned (controlled by a |
* fixes #14444; add `genLineDir` before raises * add a test case * fixes differently
…1201) * fixes nim-lang#14444; add `genLineDir` before raises * add a test case * fixes differently
…1201) * fixes nim-lang#14444; add `genLineDir` before raises * add a test case * fixes differently
…1201) * fixes nim-lang#14444; add `genLineDir` before raises * add a test case * fixes differently
originally reported here: Traceback missing line number - Nim forum
but the problem is frequent, annoying (makes debugging harder), and fixable.
Example
Current Output
Expected Output
Additional Information
in more complex cases, the lack of line number would be more problematic, eg:
The text was updated successfully, but these errors were encountered: