ceefour/wincachegrind

Call targets not found

kingma-sbw opened this issue · 10 comments

After first install WinCacheGrind and loading a grind file WinCachegrind reports error

"Cannot find call target." 
cachgrind.out line number: 20

Stack[0]: [1] php:::spl_autoload_register[[1] php:internatl: 10

cachegrind.out.1632138255.21196.zip
File attached

Screenshot of the error
Clipboard Image

@kingma-sbw

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.

@kingma-sbw

You might get better luck with QCacheGrind as it is kcachegrind ported to windows.

https://sourceforge.net/projects/qcachegrindwin/

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.

@ceefour

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!

@kingma-sbw

You might get better luck with QCacheGrind as it is kcachegrind ported to windows.

https://sourceforge.net/projects/qcachegrindwin/

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!

If anyone is running into an issue with WinCacheGrind due to an older Xdebug bug, FYI Xdebug 3 is compatible with PHP 7.2+, here is the compatibility table:
https://xdebug.org/docs/compat

WinCacheGrind still works flawless to me with Xdebug 3 (I am currently using PHP 8.0+Xdebug 3.1.6 as I am in the process of upgrading an old PHP app one PHP version at a time). I expect WinCacheGrind to work well even with PHP 8.4 and Xdebug 3.4, and the UI is much cleaner than of the alternatives.

I just tried the cachgrind file attached to the issue, and WinCacheGrind 1.1.0.16 is opening it without any issue. I think this issue could be closed.