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

Implement Dump-on-Error alternative #1395

Closed
wmdietlGC opened this issue Jul 10, 2017 · 0 comments · Fixed by #3406
Closed

Implement Dump-on-Error alternative #1395

wmdietlGC opened this issue Jul 10, 2017 · 0 comments · Fixed by #3406
Milestone

Comments

@wmdietlGC
Copy link
Contributor

One useful way of debugging Checker Framework issues was to pass -doe to javac, which "dumps-on-errors", meaning one sees a stack trace from where an error is raised.

The recent changes to collect all errors from a compilation unit and report them in BaseTypeChecker::printCollectedMessages 0c2c4f8 makes passing -doe useless, as all errors have the same stack trace.

It would be very useful for debugging if the CheckerMessage stored the stacktrace of where it was originally created and we either add a new -AdumpOnErrors flag (or reuse the existing -AprintErrorStack for this purpose) to output this additional information.

@wmdietlGC wmdietlGC added this to the High milestone Jul 10, 2017
aditya3434 added a commit to aditya3434/checker-framework that referenced this issue Jun 16, 2020
aditya3434 added a commit to aditya3434/checker-framework that referenced this issue Jun 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant