Community
Participate
Working Groups
Memory Browser View: If a valid expression is entered into the address field and evaluated then an invalid expression is entered and evaluated, on the next run control event the previously-evaluated valid expression replaces the current expression in the address field. Steps to reproduce: 1) Debug something (I used a C program) and stop at a breakpoint. 2) Enter a valid expression in the Memory Browser View and evaluate it by clicking the GO button, or entering RETURN after entry; note valid address and memory contents in address and memory contents panes. 3) Enter an invalid expression. 4) Step one statement. Note that the address field now displays the previous/valid expression. Note: The code that causes this behavior seems to appear and disappear from the MemoryBrowser class in alternating versions, thus, your mileage may vary. I'll have a fix for this in an upcoming patch that will be submitted by Randy R.
Not a platform defect, CDT defect.
Created attachment 187073 [details] Changes the scrolling logic
Ignore the attachment "Changes the scrolling logic". I added the wrong patch. Randy
Created attachment 187371 [details] Corrects "x" error handling and improper replacement of old bad expression. Andre St. Laurent created this patch. I am just posting it for him. Randy
I am taking this one to apply the patch created by Andre St. Laurent of Wind River. Randy
(In reply to comment #5) > I am taking this one to apply the patch created by Andre St. Laurent of Wind > River. > > Randy Hi Andre and Randy. For purposes of the automated IP log, it would be better if Andre himself posted the patch before you marked it with iplog+
Created attachment 187466 [details] Fixes the 'x' decoration issue This patch obsoletes the prior patch. However, Bugzilla will not allow me to mark it obsolete.
I applied Andre's patch minus the messages.properties file. Which was mistakenly edited but does not apply. Randy 781-364-2226 Pawel please review
