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
Call targets not found #9
Comments
I haven't seen activity in this repository for 6 years. I'll be surprised if they fix it. I went ahead and created an issue asking about new maintainers. |
You might get better luck with QCacheGrind as it is kcachegrind ported to windows. |
You are right @jasekiw, I no longer maintain this. So if someone honest wants to maintain or fix bugs, that's good. But I guess it's better to move on to better alternative profilers and UIs available now. |
Can you list some alternatives? I found QCacheGrind as a possible alternative that was linked from xdebug's website. Is there any others that I might be missing? Thanks for the response! |
Thanks @ceefour , you are awesome. qcachegrind is working. |
@kingma-sbw @jasekiw I have put a big note to QCacheGrind both in README and the website. |
@ceefour Awesome, thanks! |
After first install WinCacheGrind and loading a grind file WinCachegrind reports error
cachegrind.out.1632138255.21196.zip
File attached
The text was updated successfully, but these errors were encountered: