From 6cf5b7c02e14dc2597638fee673a927a59dabf84 Mon Sep 17 00:00:00 2001 From: Marc Khouzam Date: Wed, 7 Apr 2010 19:44:12 +0000 Subject: [PATCH] [307614] Use handleError() instead of handleFailure() to handle MI errors. --- .../src/org/eclipse/cdt/dsf/mi/service/MIStack.java | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/mi/service/MIStack.java b/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/mi/service/MIStack.java index 4e798d9cd95..c7386189512 100644 --- a/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/mi/service/MIStack.java +++ b/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/mi/service/MIStack.java @@ -502,7 +502,7 @@ public class MIStack extends AbstractDsfService rm.done(); } @Override - protected void handleFailure() { + protected void handleError() { // If the command fails it can be because we asked for values. // This can happen with uninitialized values and pretty printers (bug 307614) // or when visualizing tracepoints. Since asking for values was simply an optimization @@ -608,7 +608,7 @@ public class MIStack extends AbstractDsfService rm.done(); } @Override - protected void handleFailure() { + protected void handleError() { // Unable to get the values. This can happen with uninitialized values and pretty printers (bug 307614) // or when visualizing tracepoints. Either way, we try to ask for the arguments without their values, // which is better than nothing @@ -651,7 +651,7 @@ public class MIStack extends AbstractDsfService rm.done(); } @Override - protected void handleFailure() { + protected void handleError() { // Unable to get the value. This can happen with uninitialized values and pretty printers (bug 307614) // or when visualizing tracepoints. Either way, we try to ask for the variables without their values, // which is better than nothing @@ -732,7 +732,7 @@ public class MIStack extends AbstractDsfService countingRm.done(); } @Override - protected void handleFailure() { + protected void handleError() { // If the command fails it can be because we asked for values. // This can happen with uninitialized values and pretty printers (bug 307614) // or when visualizing tracepoints. Since asking for values was simply an optimization