Community
Participate
Working Groups
The expressions view and other views do not always report errors found when trying to evaluate expressions. The errors are swallowed by the logic which tracks errors per individual properties in the properties update. I introduced this bug with changes for bug 321932.
To reproduce: enter an invalid expression in the expressions view.
*** cdt cvs genie on behalf of Pawel Piech *** Bug 351898 - [expressions] Invalid expressions do not show errors in the value column. [*] http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=9970e94efa165f20e78a6db09968b707d83ab1d1 [*] http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=40ebd77d9dcf90938d864e7ea707cb385181c388
(In reply to comment #2) > *** cdt cvs genie on behalf of Pawel Piech *** Thank you git genie! I was still figuring out how to make a retro-active patch for the commit I made :-) I committed the to master and cdt_8_0
Created attachment 199698 [details] Additional patch. I added an additional guard to make sure that if a variable fails to evaluate with an error, the DMC's full expression is shown in the expressions column. This is already the case for the names column. The problem does not show up with GDB, but it does with Wind River's debugger.
*** Bug 352788 has been marked as a duplicate of this bug. ***