-
-
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
Backtrace source info lost in new compiled package image? #48020
Comments
Would be great to have a self-contained test case for this. I fixed something similar, but that was slightly different. |
At least in principle there may be circumstances where precompiling Just to see if it fixes the issue, can you easily omit |
I don't think the issue here is precompilation of |
Ok, the package is currently pretty self-contained, so I made a branch of the broken state: https://github.com/quinnj/Flate.jl/tree/jq/broken. If you dev that and do |
(It is |
Yesh, it is init related. This is enough to reproduce it module MyPkg
function __init__()
error("is this loss?")
end
end # module MyPkg and load this as a package. julia> using MyPkg
ERROR: InitError: is this loss?
during initialization of module MyPkg |
Duplicate of #47744 ? |
We get the traces for everything else except init, so I'm not sure it's the same |
On Linux I get:
|
Do we store that debuginfo as dwarf in the dylib? |
No I don't think we are using dwarf for this. We use the |
I don't have a Mac machine available while I am traveling so I would be grateful if someone else could dig in. I would use LLDB to step through the backtrace collection |
libunwind isn't finding any traces, while lldb finds them just fine. It might be an LLVM Libunwind bug. |
I get the same with LLVM libunwind 14.0.6, if it's a bug in that library it hasn't been fixed until that version (I haven't tried with v15). |
Me and @vchuravy debugged this, It's not due to libunwind, but instead lld-14 doing something wrong, while experimenting we found that lld15 and l64 both get the correct results here. Since getting llvm15 for 1.9 is a no go I will try to find the commits that fixed this and backport them. |
I don't think we can close this, it seems to be still broken on macos 12 |
|
For the record, we clarified offline the only thing that had been fixed by #48544 is #48020 (comment) (which at this point should have been a separate issue). The original issue reported here with file:line info being lost for errors thrown inside |
The solution for this is generating .dSYM files for the package images. Which requires us to ship |
Working on a locally developed package where I have an error during my
__init__
function:With the problem being
@ Flate ~/.julia/compiled/v1.10/Flate/dVx3G_ADVEb.dylib:-1
where I don't have a file + line of where the error is happening. Can produce the local package setup if that's helpful.The text was updated successfully, but these errors were encountered: