At 09:13 AM 3/9/00 -0500, you wrote:
>I am using JDE beta21 with some success on Linux (kernel
>2.2.12,JDK_1.2.2_RC4, emacs 20.5.1). I am using the debugger for a
>project that employs Beans & JSP (Jrun & Resin Servlet engines). One
>problem I have is that if I use Jdebug to start the servlet engine
>I cannot find my stderr & stdout output. My quickfix was to make a
>"javaw" shellscript that redirects them to specific files. Is there a
>better way to redirect the output?
>
The stdout and stderr should appear in the CLI (command line interface)
buffer created for each process that you launch with the debugger. You can
display the buffer by selecting JDEbug->Show Buffer->CLI.
>In spite of occasional flakiness which can probabaly be attributed to
>the newness of the Java port of the debuging interface, it is quite
>usable except that:
>* When I try to map function keys to debugger functions the "f" becomes
>a key sequence starter and can no longer be typed directly into my
>source code!
This is an unintended result of a hack that the current release uses to try
to get a function key bound to a menu command to appear on the menu itself
just like any other key. I plan to remove the hack in the next release.
>* Also, when viewing local variables, would it be possible to display
>"this" or provide access to member variables?
>
I'll look into this. In the meantime, you should be able to get the value
by using the JDEBug->Evaluate Expression.
- Paul
------------------------------------------------------------
JDE mailing list archive:
http://www.mail-archive.com/[email protected]/maillist.html
If you have a problem with the JDE, please use JDE->Help->Submit Problem
Report to prepare your query. This will insure that you include all
information that may be required to solve your problem.
