Open khatchad opened 7 years ago
Some problematic entities include:
com.ibm.wala.fixedpoint.impl.AbstractFixedPointSolver.DEBUG
com.ibm.wala.fixedpoint.impl.AbstractFixedPointSolver.verbose
com.ibm.wala.fixedpoint.impl.AbstractFixedPointSolver.MORE_VERBOSE
com.ibm.wala.ipa.callgraph.propagation.StandardSolver.DEBUG_PHASES
com.ibm.wala.dataflow.ssa.SSAInference.DEBUG
It might be more consistent to use something like the java.util.Logging
package and have things like phases be logged at a FINE
or FINER
level.
Pull requests welcome on this one. Should be a good starter bug. I agree with introducing a proper logging API
On Wed, Aug 9, 2017, 3:18 PM Raffi Khatchadourian notifications@github.com wrote:
It might be more consistent to use something like the java.util.Logging package and have things like phases be logged at a FINE or FINER level.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/wala/WALA/issues/218#issuecomment-321396994, or mute the thread https://github.com/notifications/unsubscribe-auth/AALyUWuQsGSW4ACTQidVthOrnQem0VLCks5sWjA7gaJpZM4OyN7n .
@msridhar Could add a "help wanted" label (but not sure how much that would help).
Controlling debugging and verbose output doesn't seem to be consistent. There are multiple constants being used, some of which are hard-coded and others controlled by an environmental variable. It would be great to have a consistent way to control logging.