Conditional breakpoint with expression always triggers regardless of result

Completed
Avatar
Zhoujiazhiwork
Created

I found that conditional breakpoints don’t seem to work correctly.

For example, I set a condition like: "text.Contains("Hello")"

However, the breakpoint is always triggered, no matter whether the expression evaluates to true or false. It behaves as if I didn’t set any condition at all.

 

Environment:

CLion [your exact version, e.g. 2025.2.1]

Classic CLion (not Nova)

 

Votes

0

Share

2 comments
Avatar
Anna Falevskaya
Created

Hello!

When I debug a program with LLDB in the terminal and use text.contains("Hello") as a condition for a breakpoint, I get the following error:

error: stopped due to an error evaluating condition of breakpoint 1.1: "text.contains("Hello")"
Couldn't parse conditional expression:

Do you observe other behavior on your side? Are you able to use text.Contains("Hello") as a condition when you debug a program in the terminal?

Just in case, text has the std::string type in my experiments.

0
Avatar
Zhoujiazhiwork
Created

Anna Falevskaya 

In this case, text is a custom class that has a Contains method. Today I updated to the latest version of CLion [2025.2.2] and enabled Nova, and I could not reproduce the issue. For now, ignoring the post is fine with me. 

By the way, Nova is much better than the classic CLion in terms of performance and coding experience.

0

Please sign in to leave a comment.