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

Introduce better (debug) logging for CTU #886

Closed
whisperity opened this issue Sep 7, 2017 · 1 comment
Closed

Introduce better (debug) logging for CTU #886

whisperity opened this issue Sep 7, 2017 · 1 comment
Assignees
Labels
analyzer 📈 Related to the analyze commands (analysis driver) enhancement 🌟
Milestone

Comments

@whisperity
Copy link
Contributor

... and statistical checkers, if that will ever be a thing.

Currently, if CTU mode is running, even with --verbose debug, only the following output can be get, in generic:

[] - Starting static analysis...
[] - (a clang command)

All the actions taken, or failed, during the "CTU-collect" phase are never printed to a log, which makes tracing a lot harder. Did the CTU collector hang? Did an analysis hang? The prompt can stay there for a very long time for large projects.

@whisperity whisperity added enhancement 🌟 analyzer 📈 Related to the analyze commands (analysis driver) labels Sep 7, 2017
@whisperity whisperity added this to the release 6.1 milestone Sep 7, 2017
@dkrupp
Copy link
Member

dkrupp commented Nov 7, 2017

in verbose mode log the unsuccessful clang -ast-emit calls, clang-func-map calls and output

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analyzer 📈 Related to the analyze commands (analysis driver) enhancement 🌟
Projects
None yet
Development

No branches or pull requests

4 participants