cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 25929] - enhancement to FAQ on debugging Cocoon
Date Tue, 06 Jan 2004 19:20:03 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25929>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25929

enhancement to FAQ on debugging Cocoon





------- Additional Comments From lars@huttar.net  2004-01-06 19:20 -------
I forgot to mention above, that the link currently in the documentation (JPDA -
Connection and Invocation Details) is broken. However I just found that the page
is still there under a slightly different URL, and is worth keeping a link to:
http://java.sun.com/j2se/1.4.1/docs/guide/jpda/conninv.html

Next question I'd like answered is:
Once you're in the debugger, how to you get into the code? E.g. how to set a
breakpoint, is it necessary to select the right thread, ... (being an XML/XSL
programmer rather than a Java guru, it would be very helpful to have a few hints
here).
Answers:
1) Set a breakpoint in a class. E.g.
"stop in
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.checkPipeline"
2) Enter a URL in your browser to get Cocoon to do the stuff that needs
debugging. When your breakpoint is hit, you'll get the message in jdb:
Breakpoint hit: "thread=Thread-11",
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.checkPipeline(),
line=363 bci=0
3) Use the debugger commands "print", "next", and "cont" to examine the data and
step through the code.

Mime
View raw message