You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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::printCollectedMessages0c2c4f8 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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: