Community
Participate
Working Groups
When the compiler terminates abnormally (exception) or behaves unexpectedly (warning/error/abort) a simple dump of the compiler state should be produced to aid problem diagnosis. The content and conditions under which the dump is produced should be configurable by the user but the facility should be enabled by default for exceptions. Consequently its inclusion should have negligible impact on compiler performance and footprint. The file should be attached to bug reports to give a complete and objective description of the user’s environment and support problem resolution where a testcase cannot be provided. One approach is to write a uniquely name file (using date & time) in the current directory e.g “ajcore.20040818.105200.txt” which should be human readable (it can be zipped if large) to allow the user to potentially diagnose their own problems or remove potentially sensitive data before submission. It should contain basic information such as AspectJ version, system properties and command line as well as failure information such as _full_ exception stack trace, compiler messages and internal compiler state.
Created attachment 14077 [details] Dump class and testcases A new Dump facility consisting of a single org.aspectj.weaver.Dump class with static methods to generate dump files. Configuration methods and system properties determine whether a file is produced. By default the file contains the AspectJ version, system properties, command line, full classpath and compiler messages. An extensible visitor mechanism allows classes to provide additional state information.
Matthews code is now fully integrated.
Fix released as part of AspectJ 1.2.1
