From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [remote.c] kill kill_kludge
Date: Sat, 17 May 2008 16:22:00 -0000 [thread overview]
Message-ID: <200805171256.53676.pedro@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
Hi,
kill_kludge in remote.c is no longer needed. handle_inferior_event is
no longer calling target_kill on a TARGET_WAITKIND_SIGNALLED.
case TARGET_WAITKIND_SIGNALLED:
if (debug_infrun)
fprintf_unfiltered (gdb_stdlog, "infrun:
TARGET_WAITKIND_SIGNALLED\n");
stop_print_frame = 0;
stop_signal = ecs->ws.value.sig;
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_stop_reason (SIGNAL_EXITED, stop_signal);
singlestep_breakpoints_inserted_p = 0;
stop_stepping (ecs);
return;
Because of that, the kill_kludge introduces a bug in this sequence:
target remote :9999
signal 9 (inferior exits signaled, kill_kludge is step,
but target_kill isn't called)
(restart stub)
target remote :9999 (kill_kludge isn't cleared)
kill (kill_kludge is set, so 'k' is not sent to the stub...
static void
remote_kill (void)
{
/* For some mysterious reason, wait_for_inferior calls kill instead of
mourn after it gets TARGET_WAITKIND_SIGNALLED. Work around it. */
if (kill_kludge)
{
kill_kludge = 0;
target_mourn_inferior ();
return;
}
/* Use catch_errors so the user can quit from gdb even when we aren't on
speaking terms with the remote system. */
catch_errors ((catch_errors_ftype *) putpkt, "k", "", RETURN_MASK_ERROR);
/* Don't wait for it to die. I'm not really sure it matters whether
we do or not. For the existing stubs, kill is a noop. */
target_mourn_inferior ();
}
--
Pedro Alves
[-- Attachment #2: kill_kill_kludge.diff --]
[-- Type: text/x-diff, Size: 2371 bytes --]
2008-05-17 Pedro Alves <pedro@codesourcery.com>
* remote.c (kill_kludge): Delete.
(remote_wait, remote_async_wait): Don't set it.
(remote_kill, remote_async_kill): Don't do anything with it.
---
gdb/remote.c | 24 ------------------------
1 file changed, 24 deletions(-)
Index: src/gdb/remote.c
===================================================================
--- src.orig/gdb/remote.c 2008-05-17 12:40:39.000000000 +0100
+++ src/gdb/remote.c 2008-05-17 12:41:36.000000000 +0100
@@ -3320,10 +3320,6 @@ remote_async_terminal_ours (void)
remote_async_terminal_ours_p = 1;
}
-/* If nonzero, ignore the next kill. */
-
-int kill_kludge;
-
void
remote_console_output (char *msg)
{
@@ -3527,7 +3523,6 @@ Packet: '%s'\n"),
status->kind = TARGET_WAITKIND_SIGNALLED;
status->value.sig = (enum target_signal)
(((fromhex (buf[1])) << 4) + (fromhex (buf[2])));
- kill_kludge = 1;
goto got_status;
case 'O': /* Console output. */
@@ -3754,7 +3749,6 @@ Packet: '%s'\n"),
status->kind = TARGET_WAITKIND_SIGNALLED;
status->value.sig = (enum target_signal)
(((fromhex (buf[1])) << 4) + (fromhex (buf[2])));
- kill_kludge = 1;
goto got_status;
case 'O': /* Console output. */
@@ -5272,15 +5266,6 @@ getpkt_sane (char **buf, long *sizeof_bu
static void
remote_kill (void)
{
- /* For some mysterious reason, wait_for_inferior calls kill instead of
- mourn after it gets TARGET_WAITKIND_SIGNALLED. Work around it. */
- if (kill_kludge)
- {
- kill_kludge = 0;
- target_mourn_inferior ();
- return;
- }
-
/* Use catch_errors so the user can quit from gdb even when we aren't on
speaking terms with the remote system. */
catch_errors ((catch_errors_ftype *) putpkt, "k", "", RETURN_MASK_ERROR);
@@ -5298,15 +5283,6 @@ remote_async_kill (void)
if (target_is_async_p ())
serial_async (remote_desc, NULL, 0);
- /* For some mysterious reason, wait_for_inferior calls kill instead of
- mourn after it gets TARGET_WAITKIND_SIGNALLED. Work around it. */
- if (kill_kludge)
- {
- kill_kludge = 0;
- target_mourn_inferior ();
- return;
- }
-
/* Use catch_errors so the user can quit from gdb even when we
aren't on speaking terms with the remote system. */
catch_errors ((catch_errors_ftype *) putpkt, "k", "", RETURN_MASK_ERROR);
next reply other threads:[~2008-05-17 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 16:22 Pedro Alves [this message]
2008-06-05 19:18 ` Daniel Jacobowitz
2008-06-05 21:15 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200805171256.53676.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox