-
Notifications
You must be signed in to change notification settings - Fork 112
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
How do i use this on executable built using by mingw64-qmake? #89
Comments
I guess cv2pdb is stumbling over something in your debug information. If you can make your original executable available I might have a look. Please note that DWARF5 support is limited, so if the debug information is in this format you could try generating DWARF4 instead. |
My executable is here |
Your executable uses DWARF 5 indeed. There was a recent addition to better support it that wasn't yet in a released binary. Did you try building cv2pdb from master? I now committed a tiny fix, but the version before also showed this call stack for your executable:
|
I built the project from master, but unfortunatelly i'm getting simmilar results.
When i try to load that pdb file manually into Visual Studio, i get |
I use mingw64 (gcc, gdb, mingw32-make) toolchain to build applications on Windows and i use the
qt5-static
package to produce graphical applications with all Qt libraries statically linked. I made a debug build that includes the debug information in the executable.When i run
cv2pdb
, it completes without error, but apparently the resulting pdb does not load into Visual Studio (Professional 2022) correctly, because all i see is thisI tried putting the pdb file into the same directory as the crashed executable and the dump file,
I tried adding that directory to the symbol paths in Visual Studio settings,
but no luck so far.
I also noticed that my original executable had ~60MB, but after
cv2pdb
is has ~20MB while the pdb is only ~2.5MB, so clearly incomplete.Is this scenario unsupported or do i need to setup something else?
The text was updated successfully, but these errors were encountered: