Watch view doesn't show red for error message sometimes.

[andxu]

• VSCode Version: 1.22.2
• OS Version: Win10 64Bit

Steps to Reproduce:

1. Install vscode-java-debug plugin, and start the debug and evaluate a bad expression, the error message should be shown in red, but actually it sometimes shows white:
   

While debugger gives vscode the following reponse:

 {"success":false,"message":"Constructor of a local type cannot be used in an evaluation expression","request_seq":17,"command":"evaluate","body":{"error":{"id":1000,"format":"Constructor of a local type cannot be used in an evaluation expression"}},"seq":24,"type":"response"}

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• VScode doesn't show red error messages while the debuggee reports an error during evaluation. (#48467)
• Debug:Evaluate command should add evaluated expression to Debug Console history (#39182)

[isidorn]

@andxu what does "sometimes" mean? Can you please file this with reproducable steps?
Can you also reproduce this when you debug plain javascript?
Do you see value.unavalable.error when you inspect that element?

[andxu]

[andxu]

Sometime it works fine:

[andxu]

[andxu]

Steps to repro:

1. install java debugger extension,
2. Open a folder, create a new BreakpointTest.java, and fill in the code:

class A {

    void m() {
        System.out.println("outer");
    }

    String n() {
        return "outer";
    }
}

public class BreakPointTest {
    public static void main(String[] args) {
        new BreakPointTest().go();
        int j = 0;
        new A() {
            @Override
            void m() {
                System.out.println("anonymous");
            }
        }.m();
        for (int i = 1; i <= 100; i++) {
            if (i <= 99) {
                j++;
            } else {
                System.out.println(j);
            }

        }
    }

    void go() {
        new A().m();
        class A {
            String n() {
                return "inner";
            }

            void m() {
                System.out.println("inner");
            }
        }
        new A().m();
    }

    static class A {
        String n() {
            return "middle";
        }

        void m() {
            System.out.println("middle");
        }
    }
}

3. add a watch on new A().n(), and set 2 breakpoints and then Press F5 and F5 again to hit two breakpoints.

[isidorn]

@andxu I have pushed a potential fix for this. Please try the vscode insiders tomorrow and let us know if this fixed the issue on your end

[weinand]

@andxu have you been able to verify that our fix works?