This is the mail archive of the
eclipse@sources.redhat.com
mailing list for the gcj-compiled eclipse project.
Re: good work, JUnit help
- From: Tom Tromey <tromey at redhat dot com>
- To: Jonathan LaCour <panix-lists at skinnee dot net>
- Cc: eclipse at sources dot redhat dot com
- Date: 04 Aug 2003 12:52:17 -0600
- Subject: Re: good work, JUnit help
- References: <C2B0A0D6-C68E-11D7-9F33-00039382A69A@skinnee.net>
- Reply-to: tromey at redhat dot com
>>>>> "Jonathan" == Jonathan LaCour <panix-lists@skinnee.net> writes:
Jonathan> But, I have a problem when I try to run a JUnit test, it errors out
Jonathan> with the following console message:
I don't think I've tried that yet.
Could you post the full stack trace? Usually it ends up in
workspace/.metadata/.log. That might be useful.
Anyway, an entry in the RH bugzilla would be useful. Something like
this has a pretty good chance of actually being fixed.
Jonathan> If I get my unit tests working, then I will definitely be
Jonathan> able to use this on a daily basis. Any idea how to fix this
Jonathan> problem?
Sometimes these things represent real gcj bugs. So then it is just
the usual debug-fix cycle. You can use gdb on eclipse, though it
isn't always that easy -- gdb's support for both gcj and
.so-using-applications is pretty weak :-(
The situation is much worse if the code in question is not compiled.
In that case the debugging is really hard; you have to step through
the bytecode interpreter by hand, look at the `jcf-dump' output, and
map that back to the source code. Debugging prints are easier...
Tom