From: Tom Tromey <tromey@redhat.com>
To: Jonathan LaCour <panix-lists@skinnee.net>
Cc: eclipse@sources.redhat.com
Subject: Re: good work, JUnit help
Date: Mon, 04 Aug 2003 18:59:00 -0000 [thread overview]
Message-ID: <87znipl0gu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <C2B0A0D6-C68E-11D7-9F33-00039382A69A@skinnee.net>
>>>>> "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
next prev parent reply other threads:[~2003-08-04 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 15:17 Jonathan LaCour
2003-08-04 18:59 ` Tom Tromey [this message]
2003-08-04 19:15 ` Jonathan LaCour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87znipl0gu.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eclipse@sources.redhat.com \
--cc=panix-lists@skinnee.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).