Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 331522

Summary:

[expr] doesn't clear all relevant information if expression is broken

Product:

[Eclipse Project] Platform

Reporter:

?ukasz Pogorzelski <luk.pogor>

Component:

Debug

Assignee:

Platform-Debug-Inbox <platform-debug-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

minor

Priority:

CC:

pawel.1.piech

Version:

3.6.1

Keywords:

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

stalebug

Attachments:

Description	Flags
Screenshot of bug.	none

Description ?ukasz Pogorzelski

2010-12-01 05:48:17 EST

Build Identifier: 20100917-0705

Let's assume that while debugging in the Expression View we have expanded some List and its elements. Now if we mispell expression (our list) than "variable cannot be resolved" will be shown, but below list elements doesn't disappeared.

Reproducible: Always

Steps to Reproduce:
1. Debug example code line: "List list = new ArrayList(4)";

2. When list is created add "list" variable to Expressions View and expand it to see elements.
3. Mispell list variable and see that elements doesn't disappeared.

Comment 1 Pawel Piech

2010-12-02 13:47:59 EST

Created attachment 184378 [details]
Screenshot of bug.

It does look odd, thank you for the report.  If you have a patch, I'll gladly review it.

Comment 2 ?ukasz Pogorzelski

2010-12-03 02:50:21 EST

(In reply to comment #1)
> Created an attachment (id=184378) [details]
> Screenshot of bug.
> 
> It does look odd, thank you for the report.  If you have a patch, I'll gladly
> review it.

Unfortunately, I haven't a patch.

Comment 3 Lars Vogel

2019-11-14 03:10:57 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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.