3 ms·
Which version of Julia are you using and on what platform? Windows backtraces are pretty bad, but other platforms decent. The situation on Windows is likely to
by StefanKarpinski 13y ago
Which version of Julia are you using and on what platform? Windows backtraces are pretty bad, but other platforms decent. The situation on Windows is likely to improve soon, fortunately. If you have specific problems that are reproducible, it would be great to have bug reports so we can improve things: https://github.com/JuliaLang/julia/issues https://github.com/JuliaLang/julia/issues.
- DennisP 13y agoVersion 0.2.0 on Ubuntu. I should have kept better notes. Going forward, I'll try and reproduce in small amounts of code and file reports. One was pretty silly, I used "end" as a variable name. It blew up with a syntax error on a line where I was assigning to it, but didn't tell me what line or what variable name. (But it did say something about an unexpected assignment, so it knew where the problem was, it just didn't tell me.) I've got the stacktrace issue right now with an error regarding an incorrect byte index into a unicode string. I get why that happens, just can't find what's causing it in my code. Edit: changed to an ascii string after seeing someone mention it here, now I'm getting a BoundsError in copy! at array.jl:49, and again the stacktrace tells me nothing else besides the top-level function call.