Disasterous compiler behaviour

I'm getting somewhat worried at the sorry state of compilation within IDEA in the current EAP.

First there was the jikes bug, this is partially fixed in that the compiler no longer hangs, but the problem still exists in that the error page will say that jikes could not find packages that definitely exist.

Worse, one project I work with has problems with javac too. So getting the project to compile involves a huge song and dance with switching compilers 5-6 times to eventually get everything compiled. Not exactly ideal!

The problem is that the nature of the errors make it look like it's IDEA's fault. The actual error is almost always hidden away, with no way to get at it. In the case of javac, for example, all I see is 'internal compiler error, build completed with 1 error and 0 warnings'. What the internal happens to be is a complete mystery, and isn't shown anywhere.

Similary with jikes, even if it is a jikes bug, it used to work in 3.0, can we have details of what changed such that it doesn't work in 4.0? Even though it is a jikes bug, I think it'd reflect very poorly on a 4.0 release of it had a flakey jikes compiler, even if it is jikes' fault. Does this error happen with older versions of jikes? Current CVS versions?

In my opinion, even if it does end up being my fault somehow, the compiler issue isn't production worthy until both javac and jikes work, or at least provide a clear and explicit description placing the blame on the compiler rather than making it look like IDEA is confused.

7 comments

Unfortunately it is not always possible to obtain the reason of the error that caused external process to crash. It may not be
available via output stream, so IDEA cannot read it or the process may simply terminate with the exit code != 0. The only thing we
can do here is to write that "compiler internal error" happened.
As for the jikes that cannot find packages, we'll investigate the issue further, thanks for the input on this.

--

Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Hm, whenever javac dies surely it sends something to System.out or System.err?

0

I was referring to jikes. We've reproduced a situation here that nothing can be read from streams (both standard output and error)
after jikes crashed by internal assertion. When invoked directly from command line, however, there is relevant text in the console
("Assertion failed....").

--

Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc
http://www.jetbrains.com
"Develop with pleasure!"

"Hani Suleiman" <hani@formicary.net> wrote in message news:3070611.1075566854004.JavaMail.itn@is.intellij.net...

Hm, whenever javac dies surely it sends something to System.out or System.err?



0

Ouch, yeah that sucks.

There are two issues though, with javac dying, there should be some output...hopefully! all that is shown is 'compiler internal error'

0

On 2004/01/31 09:50, Eugene Zhuravlev (JetBrains) wrote:

As for the jikes
that cannot find packages, we'll investigate the issue further,
thanks for the input on this.


Did you notice the test project I created to reproduce this problem, here?:
http://www.intellij.net/forums/thread.jsp?forum=13&thread=59622&message=792507#789654

Bas

0

Going to have to wait for the Jikes windows release for me. :(

0

Please sign in to leave a comment.