From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/4] New agent command 'kill' and used by gdbserver
Date: Thu, 21 Jun 2012 16:05:00 -0000 [thread overview]
Message-ID: <4FE34631.3080108@redhat.com> (raw)
In-Reply-To: <4FE1D4D4.4070506@codesourcery.com>
On 06/20/2012 02:49 PM, Yao Qi wrote:
> +
> +int
> +kill_inferior (int pid)
> +{
> + gdb_agent_about_to_close (pid);
"about to kill" was meant to indicate that the function does something
just before the caller kills. "about to close" sounds like the function
is called to react to the fact that the the caller is about to close
something else, but that is not what is happening, as the "about to close"
function is what really closes. gdb_agent_about_to_kill or gdb_agent_close
would sound right, but about_to_close doesn't.
> +/* Sent the agent a command to close it. */
> +
> +void
> +gdb_agent_about_to_close (int pid)
> +{
> + char buf[IPA_CMD_BUF_SIZE];
> +
> + if (!maybe_write_ipa_not_loaded (buf))
> + {
> + struct thread_info *save_inferior;
> + struct inferior_list_entry *inf = all_threads.head;
> +
> + save_inferior = current_inferior;
> +
> + /* Find a certain thread which belongs to process PID. */
> + while (inf != NULL)
> + {
> + if (ptid_get_pid (inf->id) == pid)
> + break;
> + inf = inf->next;
> + }
This is a little simpler if written as a for loop:
struct inferior_list_entry *inf;
/* Find a certain thread which belongs to process PID. */
for (inf = all_threads.head; inf != NULL; inf = inf->next)
if (ptid_get_pid (inf->id) == pid)
break;
Okay with those changes.
--
Pedro Alves
next prev parent reply other threads:[~2012-06-21 16:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 12:47 [PATCH 0/4] PR14161: a partial fix Yao Qi
2012-06-09 12:47 ` [PATCH 1/4] New test for removing socket file in gdb.trace/strace.exp Yao Qi
2012-06-12 14:51 ` Pedro Alves
2012-06-14 14:39 ` Yao Qi
2012-06-15 19:00 ` Pedro Alves
2012-06-20 13:46 ` Yao Qi
2012-06-21 15:56 ` Pedro Alves
2012-06-27 3:55 ` Yao Qi
2012-06-09 12:47 ` [PATCH 2/4] Remove socket file at exit Yao Qi
2012-06-12 15:14 ` Pedro Alves
2012-06-14 14:44 ` Yao Qi
2012-06-15 19:02 ` Pedro Alves
2012-06-09 12:47 ` [PATCH 3/4] New agent command 'kill' and used by gdbserver Yao Qi
2012-06-09 13:11 ` Eli Zaretskii
2012-06-12 16:14 ` Pedro Alves
2012-06-14 14:50 ` Yao Qi
2012-06-14 16:37 ` Eli Zaretskii
2012-06-15 19:25 ` Pedro Alves
2012-06-20 13:49 ` Yao Qi
2012-06-21 16:05 ` Pedro Alves [this message]
2012-06-09 12:47 ` [PATCH 4/4] gdb: kfail for PR14161 Yao Qi
2012-06-12 16:21 ` Pedro Alves
2012-06-14 15:01 ` Yao Qi
2012-06-15 19:33 ` Pedro Alves
2012-06-20 13:55 ` Yao Qi
2012-07-27 8:19 ` [committed] : [PATCH 0/4] PR14161: a partial fix Yao Qi
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=4FE34631.3080108@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.com \
/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