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

Cannot read calls output in callgrind_annotate #2

Open
scriptum opened this issue Jun 5, 2013 · 2 comments
Open

Cannot read calls output in callgrind_annotate #2

scriptum opened this issue Jun 5, 2013 · 2 comments

Comments

@scriptum
Copy link

scriptum commented Jun 5, 2013

Hello, I have a problem with ur calls output format - I cannot read it using callgrind_annotate with this error:

Line 1: missing command line

Maybe you are missing a "cmd" field, needed by specification?

@dkrotx
Copy link
Owner

dkrotx commented Jun 8, 2013

Hello.
Fixed in 28615ab. I never used callgrind_annotate, preferring output of crxprof itself for text-mode, and kcachegrind for GUI.
In fact, I can't say it will be helpfull, but now callgrind_annotate works at least.
Thanks for report!

@scriptum
Copy link
Author

scriptum commented Jun 8, 2013

Thanks you!

This tool is very handy to localize bugs in huge hard-to-restart applications such as Xorg.

Another little question: I ran this program as root for Xorg and twice my system was completely hanged under high load. May sometimes crxprof cause target program to halt forever?

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