An alternative to using println's is to use AspectJ.
AspectJ enables the clean modularization of crosscutting concerns such
as: error checking and handling, synchronization, context-sensitive
behavior, performance optimizations, monitoring and logging, debugging
support, and multiple obj
iously run test cases
nowadays, which does aid in isolating problems.
:ml
--JAA32418.964197274/c806001-b.pinol1.sfba.home.com--
ReSent-Date: Fri, 21 Jul 2000 09:53:42 -0700 (PDT)
ReSent-From: Man Chi Ly <[EMAIL PROTECTED]>
ReSent-To: [EMAIL PROTECTED]
ReSent-Subject: Re: Debugging Java on Linux with JDK1.
I used a commercial app called "bugseeker" and had fairly good luck
with it. It has a free 30(?) day eval period. Forte (free) also has
a debugger but i have not tried it. I believe the N.Meyer's Java-Linux
book has a simple debugger as one of its examples.
Even if you don't keep it bugseeke
On Wed, Jul 19, 2000 at 03:54:40PM +, Kris Heyrman wrote:
> Hi,
>
> I think I am getting stupid: I just spent a day trying to find out how best to
> debug a project that is getting fairly complicated, in Java. I did not find out
> how, so I am asking the question. Hopefully, somebody can give
Here's what I had to do on my system to get jdb running. It did
not run without root's help:
uname -a
Linux joi 2.2.12-20 #1 Mon Sep 27 10:40:35 EDT 1999 i686 unknown
cat /etc/issue
Red Hat Linux release 6.1 (Cartman)
Kernel 2.2.12-20 on an i686
java -version
java version "1.2.2"
Classic VM (b
For jdb
the command use should work for most class files I just tried
1.2.2 fcs and it
worked ok (perhaps run strace to see why it is not working)
I managed to use oldjdb with 1.3 and use worked ok there for simple
.class files too
For gdb you'll need to handle SIGUSR1 (the following works for
