/usr/share/doc/aspectj-doc/pdguide/index.html is in aspectj-doc 1.8.9-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>The AspectJtm Problem Diagnosis Guide</title><link rel="stylesheet" type="text/css" href="aspectj-docs.css"><meta name="generator" content="DocBook XSL Stylesheets V1.79.1"><meta name="description" content='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 . Since most errors relate to writing pointcuts incorrectly, there is a section on . 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: can be enabled to track progress up to the time of a failure; can give a relatively complete picture of the state of the world at the time of a failure; and 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.'><link rel="home" href="index.html" title="The AspectJtm Problem Diagnosis Guide"><link rel="next" href="messages.html" title="Chapter 1. Messages"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">The AspectJ<sup>tm</sup> Problem Diagnosis Guide</th></tr><tr><td width="20%" align="left"> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="messages.html">Next</a></td></tr></table><hr></div><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="idm1"></a>The AspectJ<sup>tm</sup> Problem Diagnosis Guide</h1></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="othername">the AspectJ Team</span></h3></div></div></div><div><div class="legalnotice"><a name="idm8"></a><p>Copyright (c) 2006 IBM Corporation and others.
2006 Contributors.
All rights reserved.
</p></div></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
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.
</p><p>
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 <a class="xref" href="messages.html" title="Chapter 1. Messages">Messages</a>. Since most errors
relate to writing pointcuts incorrectly, there is a section on
<a class="xref" href="pointcuts.html" title="Chapter 2. Debugging Pointcuts">Debugging Pointcuts</a>.
</p><p>
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:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p><a class="xref" href="trace.html" title="Chapter 4. Tracing">Tracing</a> can be enabled to track progress up to the time of a failure;</p></li><li class="listitem"><p><a class="xref" href="ajcore.html" title="Chapter 3. AspectJ Core Files">AspectJ Core Files</a> can give a relatively complete picture of the state of
the world at the time of a failure; and </p></li><li class="listitem"><p><a class="xref" href="ltwdump.html" title="Chapter 5. Dumping classes during load-time weaving">Dumping classes during load-time weaving</a> is a way to capture both
input and output classes during load-time weaving.
</p></li></ol></div><p>
</p><p>
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.
</p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="messages.html">1. Messages</a></span></dt><dd><dl><dt><span class="sect1"><a href="messages.html#messages-introduction">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="messages.html#messages-introduction-config">Configuring Messages</a></span></dt></dl></dd><dt><span class="sect1"><a href="messages-scenarios.html">Message scenarios</a></span></dt><dd><dl><dt><span class="sect2"><a href="messages-scenarios.html#messages-scenarios-ct">Compile-time weaving scenarios</a></span></dt><dt><span class="sect2"><a href="messages-scenarios.html#messages-scenarios-ltw">Load-time weaving scenarios</a></span></dt></dl></dd><dt><span class="sect1"><a href="messages-xlint.html">Lint messages</a></span></dt></dl></dd><dt><span class="chapter"><a href="pointcuts.html">2. Debugging Pointcuts</a></span></dt><dd><dl><dt><span class="sect1"><a href="pointcuts.html#pointcuts-introduction">Introduction</a></span></dt><dt><span class="sect1"><a href="pointcuts-debugging.html">Debugging pointcuts</a></span></dt></dl></dd><dt><span class="chapter"><a href="ajcore.html">3. AspectJ Core Files</a></span></dt><dd><dl><dt><span class="sect1"><a href="ajcore.html#ajcore-introduction">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ajcore.html#configuration">Configuring dump files</a></span></dt><dt><span class="sect2"><a href="ajcore.html#ajcore-examples">AJCore File Examples</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="trace.html">4. Tracing</a></span></dt><dd><dl><dt><span class="sect1"><a href="trace.html#trace-introduction">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="trace.html#trace-configuration">Configuring Tracing</a></span></dt><dt><span class="sect2"><a href="trace.html#trace-examples">Examples</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ltwdump.html">5. Dumping classes during load-time weaving</a></span></dt><dd><dl><dt><span class="sect1"><a href="ltwdump.html#ltwdump-introduction">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="ltwdump.html#ltw-examples">Configuring bytecode dumping in load-time weaving</a></span></dt><dt><span class="sect2"><a href="ltwdump.html#ltwdump-examples">LTW Dump Examples</a></span></dt></dl></dd></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="messages.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"> </td><td width="40%" align="right" valign="top"> Chapter 1. Messages</td></tr></table></div></body></html>
|