From c341b5b3294f13eb93f012ef0c051f8d6b187ca8 Mon Sep 17 00:00:00 2001 From: John Cortell Date: Mon, 11 Jan 2010 22:46:57 +0000 Subject: [PATCH] [299323] Scrolling through invalid memory grows the Eclipse error log --- .../cdt/debug/ui/memory/traditional/Rendering.java | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/memory/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional/Rendering.java b/memory/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional/Rendering.java index a4df5cff73c..714a8338ac7 100644 --- a/memory/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional/Rendering.java +++ b/memory/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional/Rendering.java @@ -1004,9 +1004,12 @@ public class Rendering extends Composite implements IDebugEventSetListener } catch(Exception e) { - logError( - TraditionalRenderingMessages - .getString("TraditionalRendering.FAILURE_READ_MEMORY"), e); //$NON-NLS-1$ + // User can scroll to any memory, whether it's valid on the + // target or not. Doesn't make much sense to fill up the Eclipse + // error log with such "failures". +// logError( +// TraditionalRenderingMessages +// .getString("TraditionalRendering.FAILURE_READ_MEMORY"), e); //$NON-NLS-1$ } }