Re: [platform-debug-dev] Collapsing register tree or no source updates:

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [platform-debug-dev] Collapsing register tree or no source updates: pick your poison?

From: Darin Wright <Darin_Wright@xxxxxxxxxx>
Date: Mon, 29 May 2006 10:00:32 -0500
Delivered-to: platform-debug-dev@xxxxxxxxxxx
List-archive: <http://eclipse.org/pipermail/platform-debug-dev>
List-help: <mailto:platform-debug-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/platform-debug-dev>, <mailto:platform-debug-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/platform-debug-dev>, <mailto:platform-debug-dev-request@eclipse.org?subject=unsubscribe>

> > In Eclipse 3.1, we forced source-locator updates by firing CHANGE events > from the stack frame whenever execution suspended, but this doesn't > appear to have any effect in Eclipse 3.2. >
Ken, it looks like this is a regression in 3.2. Please file a bug against the debug platform. Not sure if we will fix this in 3.2, or wait for 3.2.1.

Darin

References:
- [platform-debug-dev] Collapsing register tree or no source updates: pick your poison?
  - From: Ken_Dyck

Prev by Date: RE: [platform-debug-dev] Collapsing register tree or no source updates: pick your poison?
Next by Date: RE: [platform-debug-dev] Collapsing register tree or no source updates: pick your poison?
Previous by thread: Re: [platform-debug-dev] Collapsing register tree or no source updates: pick your poison?
Next by thread: RE: [platform-debug-dev] Collapsing register tree or no source updates: pick your poison?
Index(es):
- Date
- Thread

Breadcrumbs