You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

index.adoc 2.1KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344
  1. = The AspectJ^TM^ Problem Diagnosis Guide
  2. :doctype: book
  3. :leveloffset: +1
  4. _by the AspectJ Team_
  5. _Copyright (c) 2006 IBM Corporation and others. 2006 Contributors. All rights reserved._
  6. This guide describes how to configure the AspectJ compiler/weaver to provide
  7. information for diagnosing problems in the input programs, the
  8. compiler/weaver or its configuration.
  9. The AspectJ compiler and weaver can provide lots of information for diagnosing
  10. problems in building AspectJ programs. For problems in the input program,
  11. there are a number of default warning and error messages, as well as many
  12. configurable "lint" messages, all of which can be emitted normally,
  13. logged using standard facilities, or intercepted programmatically.
  14. These are discussed in xref:messages.adoc#messages[Messages]. Since most errors
  15. relate to writing pointcuts incorrectly, there is a section on
  16. xref:pointcuts.adoc#pointcuts[Debugging Pointcuts].
  17. For problems with the compiler/weaver itself there are three facilities
  18. that enable the AspectJ developers to resolve bugs even when it is
  19. too hard to deliver a reproducible test case:
  20. * xref:trace.adoc#trace[Tracing] can be enabled to track progress up to the time of a failure;
  21. * xref:ajcore.adoc#ajcore[AspectJ Core Files] can give a relatively complete picture of the state of
  22. the world at the time of a failure; and
  23. * xref:ltwdump.adoc#ltwdump[Dumping classes during load-time weaving] is a way to capture both input and output classes during load-time weaving.
  24. This guide describes how to configure messages to get the right information
  25. and how to configure traces, dumps, and core files. Although the compiler/weaver
  26. operates in roughly three modes (from the command-line, embedded in an IDE,
  27. and enabled as load-time weaving), the principles are basically the same for
  28. all modes. The differences lie in how to set up diagnostics and what
  29. information is likely to be relevant.
  30. **Table of Contents**
  31. * xref:messages.adoc[Messages]
  32. * xref:pointcuts.adoc[Debugging Pointcuts]
  33. * xref:trace.adoc[Tracing]
  34. * xref:ajcore.adoc[AspectJ Core Files]
  35. * xref:ltwdump.adoc[Dumping classes during load-time weaving]