-
Notifications
You must be signed in to change notification settings - Fork 0
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
Crash-reporter doesn't seem to work correctly without Python installed?? #15
Comments
Note that this issue was (as I now installed the package) reproducible on my Can first compare both chocolatey packages, as both machines are up to date.
yes | pacman -S mingw-w64-x86_64-gdb solves the issue. (
restores the issue. Removing Let's try to grep $ grep -r 'msys64'
grep: gdb/gdb.exe: binary file matches
grep: libtermcap-0.dll: binary file matches
grep: libintl-8.dll: binary file matches
grep: libpython3.10.dll: binary file matches
grep: libreadline8.dll: binary file matches |
Noe Lajoie has the same issue. |
Should also produce cleaner crash reports not containing something like |
|
|
As of today my Framework Windows trust VM has the issue but snapshotting no matter my current snapshotting error would be very helpful otherwise it could be a headache to understand the issue source. Note that my only Windows trust VM on Pegasus does not face the issue. Framework Windows not trust VM also has the gdb issue but has the same snapshotting issue. Well as I have 2 VMs having the issue, let us find the solution on one and try this solution on the other. |
New version of gdb now leads to:
Even if copy:
|
Note that assuming that
D:\\a\\
meansc:\\tools\\
, then all files/folders exist, except that there are no.zip
,lib-dynload
and now it ispython3.11
and notpython3.10
. Hence giving a try rebuilding to have latest Python seems to make sense.Discord user:
1130419636664553564
- don't contact him, as he is aggressive for no reason.Note that this computer is under Windows 10 otherwise it's up to date.
The error message mentions
msys
butmsys2
returns:on his machine while on my VirtualBox it doesn't return anything and launch a msys prompt.
Maybe it's because the gdb version that I share was compiled on msys...
Still have the issue after restarting to make sure that the recent
choco install python
wasn't problematic.So it definetely seems that my gdb build on msys is to blame...
The text was updated successfully, but these errors were encountered: