aboutsummaryrefslogtreecommitdiff
path: root/gdb/tracepoint.c
diff options
context:
space:
mode:
authorHui Zhu <teawater@gmail.com>2011-07-07 13:32:55 +0000
committerHui Zhu <teawater@gmail.com>2011-07-07 13:32:55 +0000
commit26afc0d7031bc2041ea17a4c25b04454b4e4feab (patch)
treedc4d9c155635214de37835f606358ce9cf688f3b /gdb/tracepoint.c
parentcff32a7c64a02339aed9f2d5f88d33e1396dad1d (diff)
downloadgdb-26afc0d7031bc2041ea17a4c25b04454b4e4feab.zip
gdb-26afc0d7031bc2041ea17a4c25b04454b4e4feab.tar.gz
gdb-26afc0d7031bc2041ea17a4c25b04454b4e4feab.tar.bz2
2011-07-07 Hui Zhu <teawater@gmail.com>
Revert: 2011-07-06 Hui Zhu <teawater@gmail.com> * remote.c (remote_start_remote): Add TRY_CATCH for remote_get_trace_status. * tracepoint.c (disconnect_tracing): Ditto.
Diffstat (limited to 'gdb/tracepoint.c')
-rw-r--r--gdb/tracepoint.c14
1 files changed, 1 insertions, 13 deletions
diff --git a/gdb/tracepoint.c b/gdb/tracepoint.c
index 4c54d2d..2d62f4d 100644
--- a/gdb/tracepoint.c
+++ b/gdb/tracepoint.c
@@ -1900,23 +1900,11 @@ trace_status_mi (int on_stop)
void
disconnect_tracing (int from_tty)
{
- int ret = 0;
- volatile struct gdb_exception ex;
-
/* It can happen that the target that was tracing went away on its
own, and we didn't notice. Get a status update, and if the
current target doesn't even do tracing, then assume it's not
running anymore. */
- TRY_CATCH (ex, RETURN_MASK_ERROR)
- {
- ret = target_get_trace_status (current_trace_status ());
- }
- if (ex.reason < 0)
- {
- warning (_("%s"), ex.message);
- ret = -1;
- }
- if (ret < 0)
+ if (target_get_trace_status (current_trace_status ()) < 0)
current_trace_status ()->running = 0;
/* If running interactively, give the user the option to cancel and