Why do I keep getting “Evaluations must contain either an expression or a block of well-formed statements”?

Question

In my code, I am trying to output the value of src in the expressions window.

public void doIt() {
    String src = \"test\";
    System.out.pri         


        

Answer 1

If your code use any generics, you may want to check this bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=341232

Occurs in all version of Eclipse up to 4.2. In short certain generics expressions cause Eclipse to completely fail on any evaluation (please see this example: https://bugs.eclipse.org/bugs/attachment.cgi?id=224760). Not sure whether your code uses any generics, but if so, this may be it. Note that it is enough to have one of the troublesome generics somewhere in your class, not necessary in your method.

Answer 2

According to https://stackoverflow.com/a/21763943/733092, this happens when the class contains a generic method like

public <T extends something> T myMethod() {};

Answer 3

Check if you have updated version of Eclipse, looks like this issue is fixed in Eclipse 3.3

My Eclipse Version is 3.8.2 and if I evaluate the expression on line 2 then I am also receiving the same error but at line 3 its evaluating properly.

Answer 4

I had the same problem and I remove a generic method in my code. It work for me.

Answer 5

I just spent TONS of time to figure out that if you will create a package "Foo" and inside this package you'll create class called "Foo", like this:

package Foo;

public class Foo{
    public Foo () {};
}

After the point when you use this class first time in your program, you will not be able to use expressions anymore:

import Foo.Foo; //this is the devil i think

public static void main(String[] args){
    EventQueue.invokeLater(new Runnable(){
        public void run(){
            //debug expressions works fine
            Foo tmp = new Foo();
            //debug expressions wouldn't work anymore
        }
    });
}

This bug can be reprodused up to current Eclipse Neon 4.7.

Answer 6

(Assuming you're compiling 1.5+ code)I had the same problem, here's what I did to fix it:

• Ensure that your java compiler version is 1.5+
• Fix all syntax/class related errors pertaining to that class. I had a number of missing dependencies in my classpath.
• make sure the JRE is also 1.5+ for that specific project