This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH] Remove obsolete TARGET_WAITKIND_SIGNALLED comment.


Twelve years have passed since this comment was added, at

 http://sourceware.org/ml/gdb-patches/2000-04/msg00015.html

There's no way it could ever be useful nowadays.  On the contrary,
it's just confusing for newcomers.  I remember it confused me.

Time to zap it.  Applied.

gdb/
2012-10-26  Pedro Alves  <palves@redhat.com>

	* infrun.c (handle_inferior_event) <TARGET_WAITKIND_SIGNALLED>:
	Remove comment.
---
 gdb/infrun.c |    5 -----
 1 file changed, 5 deletions(-)

diff --git a/gdb/infrun.c b/gdb/infrun.c
index eb97c52..5479486 100644
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -3406,11 +3406,6 @@ handle_inferior_event (struct execution_control_state *ecs)
       stop_print_frame = 0;
       target_terminal_ours ();	/* Must do this before mourn anyway.  */
 
-      /* Note: By definition of TARGET_WAITKIND_SIGNALLED, we shouldn't
-         reach here unless the inferior is dead.  However, for years
-         target_kill() was called here, which hints that fatal signals aren't
-         really fatal on some systems.  If that's true, then some changes
-         may be needed.  */
       target_mourn_inferior ();
 
       print_signal_exited_reason (ecs->ws.value.sig);


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]