-
Notifications
You must be signed in to change notification settings - Fork 570
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
Compatibility issues with .NET AoT-compiled binaries #2473
Comments
@Still34 Do you happen to have a test binary available? If not, I can certainly reproduce it on my side, but it might take an extra 30 mins or more of effort. |
|
native.zip |
The |
I can't reproduce with the provide native.zip and current master (and viv-utils==0.7.9, vivisect==1.2.1). Can you confirm you're still encountering this? I know it's been a while since this was reported. |
Problem 1 still occurs to me with the specified package versions. Problem 2 is dupe of #2497. |
Hmm, still works for me... Linux
Python 3.11.9 here it also works: https://github.com/mandiant/capa-testfiles/actions/runs/12176598949/job/33962675371?pr=270 Maybe it's an issue on Windows?! |
I'm also unable to reproduce on Linux: But I do suspect this might be Windows-specific, since the stack trace identifies vtrace win32 routines, which I believe use the Windows PDB parser. We can report the bug upstream to vivisect, and in the meantime, a workaround is to use the Linux build. Unfortunately, since the bug is encountered during workspace creation, there's not anything we can do from the capa side to ignore it. |
Description
Using the now-latest commit d4d8567, feeding capa a .NET 8.0 Ahead-of-Time compiled binary causes multiple issues to crop up.
Unhandled Variant Type: 21
, but the standalone version is still able to finish the analysis and display the resultsSteps to Reproduce
dotnet new console
)dotnet publish -c release -r win-x64 /p:PublishAot=true /p:PublishSingleFile=false
)Expected behavior:
Finish the analysis without errors
Actual behavior:
Errors show up
Versions
Additional Information
The text was updated successfully, but these errors were encountered: