From: Pedro Alves Date: Thu, 14 Nov 2013 19:43:25 +0000 (+0000) Subject: infrun.c:handle_inferior_event: Move comment. X-Git-Tag: gdb-7.7-release~514 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=05ba85103b9131333b829c7c1366bfdb015169a3;p=external%2Fbinutils.git infrun.c:handle_inferior_event: Move comment. This comment applies to the whole handle_inferior_event flow, top to bottom. Best move it to the function's intro. gdb/ 2013-11-14 Pedro Alves * infrun.c (handle_inferior_event): Move comment from the function's body to the function's description, adjusted. --- diff --git a/gdb/ChangeLog b/gdb/ChangeLog index e85ceea..31c32ca 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,10 @@ 2013-11-14 Pedro Alves + * infrun.c (handle_inferior_event): Move comment from the + function's body to the function's description, adjusted. + +2013-11-14 Pedro Alves + * infrun.c (handle_inferior_event) : Handle STOP_QUIETLY_NO_SIGSTOP and STOP_QUIETLY_REMOTE here. Assert we never fall through out of the TARGET_WAITKIND_LOADED diff --git a/gdb/infrun.c b/gdb/infrun.c index ba55686..8ab6b61 100644 --- a/gdb/infrun.c +++ b/gdb/infrun.c @@ -3139,9 +3139,18 @@ fill_in_stop_func (struct gdbarch *gdbarch, } } -/* Given an execution control state that has been freshly filled in - by an event from the inferior, figure out what it means and take - appropriate action. */ +/* Given an execution control state that has been freshly filled in by + an event from the inferior, figure out what it means and take + appropriate action. + + The alternatives are: + + 1) stop_stepping and return; to really stop and return to the + debugger. + + 2) keep_going and return; to wait for the next event (set + ecs->event_thread->stepping_over_breakpoint to 1 to single step + once). */ static void handle_inferior_event (struct execution_control_state *ecs) @@ -4166,14 +4175,6 @@ Cannot fill $_exitsignal with the correct signal number.\n")); } } - /* Look at the cause of the stop, and decide what to do. - The alternatives are: - 1) stop_stepping and return; to really stop and return to the debugger, - 2) keep_going and return to start up again - (set ecs->event_thread->stepping_over_breakpoint to 1 to single step once) - 3) set ecs->random_signal to 1, and the decision between 1 and 2 - will be made according to the signal handling tables. */ - if (ecs->event_thread->suspend.stop_signal == GDB_SIGNAL_TRAP && stop_after_trap) {