compiler internal error, exit code 1

for some reason, my scala code won't compile anymore. is there anything i can do to find
out why?

9 comments
Comment actions Permalink

Hamster, dude, you've got to give more information!


RRS

0
Comment actions Permalink

it seems the project is broken. if i delete all scala files except a hello world -> still crashes
new project -> new module -> hello world -> works
new module in old project -> crash

0
Comment actions Permalink

i dont' have more information

0
Comment actions Permalink

now i have more information:
2010-03-13 22:06:47,833 [  16139]   INFO - ij.compiler.impl.CompileDriver - COMPILATION STARTED
2010-03-13 22:06:47,984 [  16290]   INFO - lij.compiler.impl.CompilerUtil - Initial VFS refresh took 94 ms: 0 min 0sec
2010-03-13 22:06:48,258 [  16564]  DEBUG - la.compiler.ScalacOutputParser - scalac error: Parameter '-reset' is not recognised by Scalac.
2010-03-13 22:06:48,258 [  16564]  DEBUG - la.compiler.ScalacOutputParser - scalac error: Parameter '-reset' is not recognised by Scalac.
2010-03-13 22:06:48,258 [  16564]  DEBUG - la.compiler.ScalacOutputParser -   scalac -help  gives more information
2010-03-13 22:06:48,258 [  16564]  DEBUG - la.compiler.ScalacOutputParser -   scalac -help  gives more information
2010-03-13 22:06:48,258 [  16564]  DEBUG - la.compiler.ScalacOutputParser - scalac error: bad option: '-reset'
2010-03-13 22:06:48,258 [  16564]  DEBUG - la.compiler.ScalacOutputParser - scalac error: bad option: '-reset'
2010-03-13 22:06:48,258 [  16564]  DEBUG - la.compiler.ScalacOutputParser -   scalac -help  gives more information
2010-03-13 22:06:48,258 [  16564]  DEBUG - la.compiler.ScalacOutputParser -   scalac -help  gives more information
2010-03-13 22:06:48,586 [  16892]  DEBUG - la.compiler.ScalacOutputParser -  
2010-03-13 22:06:48,586 [  16892]  DEBUG - la.compiler.ScalacOutputParser -  
2010-03-13 22:06:48,586 [  16892]  DEBUG - la.compiler.ScalacOutputParser -  
2010-03-13 22:06:48,586 [  16892]  DEBUG - la.compiler.ScalacOutputParser -  
2010-03-13 22:06:48,663 [  16969]   INFO - lij.compiler.impl.CompilerUtil -     COMPILATION FINISHED; Errors: 1; warnings: 0 took 830 ms: 0 min 0sec

took me a while to find the secret logging option

weird thing is, i could not reproduce this error...it just appeared at a random point in time and wouldn't go away until i figured out i had to switch "reset fsc" off. it didn't matter if "use fsc" was checked or not. unchecking everything fixed the problem.

0
Comment actions Permalink

I'm not really sure, but I have the impression that the fsc support is 2.8 specific. I hope one of the Scala plug-in principals will clarify that.

This also brings up the point that you've told us nothing about things such as:

- IDEA version
- Scala plug-in version
- Scala version
- Java version
- Operating system
- Processor architecture

In the future, you really should make it a habit to include this information when you're reporting a problem.


Randall Schulz

0
Comment actions Permalink

- IDEA version
- Scala plug-in version
- Scala version
-  Java version
- Operating system
- Processor architecture

if i had a more specific error message, i would have given some information - but "internal error" just gave me no hint what information could help.
i tried different builds of idea, the scala plugin, scala and different java versions, but the error persisted

0
Comment actions Permalink
"... but "internal error" just gave me no hint what information could help. ..."


No error report should omit those things. As a programmer, you should know that.

And you still haven't supplied them.


Randall Schulz

0
Comment actions Permalink

Try to remove project caches. Press 'Invalidate caches' in File menu. Project can't be corrupted, only caches for this project.

Best regards,
Alexander Podkhalyuzin.

0
Comment actions Permalink

i enabled the secret scala compiler logging option in some xml file and got the error message that "reset" is an unknown option. i looked at my compiler settings -> there is was, the evil checkbox. unchecked it, problem fixed.

0

Please sign in to leave a comment.