Bug 577775 - Condition on breakpoint does not work
Summary: Condition on breakpoint does not work
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.18   Edit
Hardware: PC Linux
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-13 08:53 EST by Martin Frydl CLA
Modified: 2023-12-04 02:09 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Frydl CLA 2021-12-13 08:53:44 EST
I'm trying to set breakpoint at FileInputStream(File) constructor with following condition:

file != null && file.toString().endsWith("stdout")

All I get is error "Evaluation must contain either an expression or a block of well-formed statements". Not informative at all, especially when the condition is perfectly correct. When I copy it to place where I have "java.io.File file" variable, it compiles perfectly. And there is probably local variable info present as when debugger stops there (complaining about uncompilable condition), variables window contains "file" variable with the correct value.

Even simplest condition (file != null) does not compile.

Eclipse version: 2020-12 (4.18.0)
Eclipse build: 20201210-1552
Java 11
Comment 1 Eclipse Genie CLA 2023-12-04 02:09:28 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.