-
-
Notifications
You must be signed in to change notification settings - Fork 5.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
Backtraces are broken on OSX #7821
Comments
Working on it. |
Actually, never mind. This issue is simple. You need the .dSYM files for libjulia. Try |
I suppose we should give you approximations to the backtrace (function names only, no line numbers), if the debug info is not available. |
I ran |
Ok, will have another look. |
Same thing on linux. We should also print nothing instead of the |
Ok, there is a similar issue with profiling in that I/O time is not reported properly on OS X because our unwinder fails miserably (also potentially a problem for ^C and one of the reasons we can segfault in I/O):
Just noting it down while we're talking about backtraces. I'll have a look at the other issue though. |
While working on the |
Ok, so this turns out to be mostly easy. I'll enable debug symbols in the release binaries and add a fallback mode that finds the function but bails on line numbers. |
I should note that the debug build fares much better, but is not perfect:
|
I noticed this on Linux ever since I upgraded to Kubuntu 14.04. It was better on 12.04. |
It's working fine for me locally, and wow is this a nice improvement! But very curiously it looks like this has Travis failures. It's not finding |
Fixed in the next commit. |
I should have checked. Thanks. |
@Keno wow, this is so much better. Thank you! Just one final note, there is still a single
Looking at |
In the case where we print the instruction pointer, we should print |
Yep, will do. I do think I can fix this one though. |
Well this is new. Backtraces appear to be broken on OSX, but only for C code. Example with my favorite call graph exploration utility
@profile
:This is running on:
The text was updated successfully, but these errors were encountered: