Skip to content
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

QT 6.7 Target not responding #983

Closed
Snolandia opened this issue Apr 19, 2024 · 2 comments
Closed

QT 6.7 Target not responding #983

Snolandia opened this issue Apr 19, 2024 · 2 comments

Comments

@Snolandia
Copy link

All self tests passed. Any sort of gui just closes itself and doesnt do anything. Not sure where to go from here.

The examples that came with the code also did not work.

gammaray.exe --pid 16160
Detected ABI qt6_7-GNU-x86_64, using ABI qt6_7-GNU-x86_64.
Target not responding - timeout. Try setting the env variable GAMMARAY_LAUNCHER_TIMEOUT to a bigger value (in seconds).
See https://github.com/KDAB/GammaRay/wiki/Known-Issues for troubleshooting

gammaray.exe --version
GammaRay version 3.0.95
┬⌐ Klaralvdalens Datakonsult AB, a KDAB Group company, [email protected]
Protocol version 38
Broadcast version 2

Launching with terminal and -i style offers a different error that isnt seen elsewhere

Detected ABI qt6_7-GNU-x86_64, using ABI qt6_7-GNU-x86_64.
Loading probe DLL failed: "Cannot load library C:\Program Files (x86)\GammaRay\plugins\gammaray\3.0\qt6_7-GNU-x86_64\gammaray_probe.dll: The specified module could not be found."
Target not responding - timeout. Try setting the env variable GAMMARAY_LAUNCHER_TIMEOUT to a bigger value (in seconds).
See https://github.com/KDAB/GammaRay/wiki/Known-Issues for troubleshooting

But gammaray_probe.dll is in that exact file and exact location.

Not really sure where to go from here.

@Waqar144
Copy link
Contributor

Loading probe DLL failed: "Cannot load library C:\Program Files (x86)\GammaRay\plugins\gammaray\3.0\qt6_7-GNU-x86_64\gammaray_probe.dll: The specified module could not be found."
..
But gammaray_probe.dll is in that exact file and exact location.

But probably something it depends on wasn't found, so the dll load fails. You need to debug what's missing. The internet says you can use sysinternals procmon or loader snaps

@Waqar144
Copy link
Contributor

seems duplicate of #959

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants