-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
symbolicli quietly fails to symbolize if cabextract is not found in PATH #1172
Comments
I've found in crates/symbolicator-service/src/caching/fs.rs:
So I guess I have a failed symcache conversion. I have run |
I tried rebuilding symbolicator today on a different machine and all of a sudden the problem is gone. It now is able to symbolize the minidump correctly. I'll close the issue. |
Back on the machine where I first had this problem it still occurs with the same build and I did some troubleshooting and managed to identify the problem. symbolicli tries to run cabextract and if that program is not found in the PATH symbolization quietly fails and the only evidence is |
I'm trying to use symbolicli to analyze minidumps in offline mode and it only symbolizes very few symbols in the stacktraces, the rest come back unresolved.
Environment
Commit 271386c built with
cargo build --release
on Fedora 37 x86_64.Steps to Reproduce
My
~/.symboliclirc
:Command executed:
Expected Result
I hoped to get a stacktrace back with function names resolved
Actual Result
Functions are mostly not resolved, with a few exceptions:
Using the same symbol servers Visual Studio 2022 symbolizes the same minidump correctly.
I had a look in the files in the cache directory and a bunch of them report a weird looking error. I think this may be the cause of the problem?
The accompanying .txt file in the cache to one of those reporting malformed above points to a debug source file that exists:
Could this possibly be related to the use of layout type "symstore_index2"?
The text was updated successfully, but these errors were encountered: