diff options
author | Alexander Kriegisch <Alexander@Kriegisch.name> | 2022-01-08 11:50:55 +0700 |
---|---|---|
committer | Alexander Kriegisch <Alexander@Kriegisch.name> | 2024-01-06 10:09:11 +0100 |
commit | d4a6906b3012fac6e4dbaca5854fc59ba0d67e47 (patch) | |
tree | c78540555837c12cfaef7f9cc95842668a3ee7f9 /docs/pdguide/pdguide.adoc | |
parent | 9735e858af48ff0bce152ea489800a86a151b08d (diff) | |
download | aspectj-d4a6906b3012fac6e4dbaca5854fc59ba0d67e47.tar.gz aspectj-d4a6906b3012fac6e4dbaca5854fc59ba0d67e47.zip |
Rename '*GuideDB' directories to their actual HTML site target names
Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
Diffstat (limited to 'docs/pdguide/pdguide.adoc')
-rw-r--r-- | docs/pdguide/pdguide.adoc | 50 |
1 files changed, 50 insertions, 0 deletions
diff --git a/docs/pdguide/pdguide.adoc b/docs/pdguide/pdguide.adoc new file mode 100644 index 000000000..dcbcfc331 --- /dev/null +++ b/docs/pdguide/pdguide.adoc @@ -0,0 +1,50 @@ += The AspectJ^TM^ Problem Diagnosis Guide + +:doctype: book + +_by the AspectJ Team_ + +_Copyright (c) 2006 IBM Corporation and others. 2006 Contributors. All rights reserved._ + +This guide describes how to configure the AspectJ compiler/weaver to provide +information for diagnosing problems in the input programs, the +compiler/weaver or its configuration. + +The AspectJ compiler and weaver can provide lots of information for diagnosing +problems in building AspectJ programs. For problems in the input program, +there are a number of default warning and error messages, as well as many +configurable "lint" messages, all of which can be emitted normally, +logged using standard facilities, or intercepted programmatically. +These are discussed in xref:messages.adoc#messages[Messages]. Since most errors +relate to writing pointcuts incorrectly, there is a section on +xref:pointcuts.adoc#pointcuts[Debugging Pointcuts]. + +For problems with the compiler/weaver itself there are three facilities +that enable the AspectJ developers to resolve bugs even when it is +too hard to deliver a reproducible test case: + +* xref:trace.adoc#trace[Tracing] can be enabled to track progress up to the time of a failure; +* xref:ajcore.adoc#ajcore[AspectJ Core Files] can give a relatively complete picture of the state of + the world at the time of a failure; and +* xref:ltwdump.adoc#ltwdump[Dumping classes during load-time weaving] is a way to capture both input and output classes during load-time weaving. + +This guide describes how to configure messages to get the right information +and how to configure traces, dumps, and core files. Although the compiler/weaver +operates in roughly three modes (from the command-line, embedded in an IDE, +and enabled as load-time weaving), the principles are basically the same for +all modes. The differences lie in how to set up diagnostics and what +information is likely to be relevant. + +//// +ATTENTION: Please do not remove blank lines in between 'include::' statements. Otherwise, section numbers in the +table of contents (TOC) can be wrong and the first section of each document missing completely. +//// +include::messages.adoc[Messages] + +include::pointcuts.adoc[Debugging Pointcuts] + +include::trace.adoc[Tracing] + +include::ajcore.adoc[AspectJ Core Files] + +include::ltwdump.adoc[Dumping classes during load-time weaving] |