From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 02/18] Remote all-stop-on-top-of-non-stop
Date: Sat, 24 Oct 2015 22:39:00 -0000 [thread overview]
Message-ID: <86vb9x1u2h.fsf@gmail.com> (raw)
In-Reply-To: <1444836486-25679-3-git-send-email-palves@redhat.com> (Pedro Alves's message of "Wed, 14 Oct 2015 16:27:50 +0100")
Pedro Alves <palves@redhat.com> writes:
> @@ -2636,8 +2633,37 @@ attach_command_post_wait (char *args, int from_tty, int async_exec)
> target_post_attach (ptid_get_pid (inferior_ptid));
>
> post_create_inferior (¤t_target, from_tty);
> +}
> +
> +/* What to do after the first program stops after attaching. */
> +enum attach_post_wait_mode
> +{
> + /* Do nothing. Leaves threads as they are. */
> + ATTACH_POST_WAIT_NOTHING,
> +
> + /* Re-resume threads that are marked running. */
> + ATTACH_POST_WAIT_RESUME,
> +
> + /* Stop all threads. */
> + ATTACH_POST_WAIT_STOP,
> +};
> +
> +/* Called after we've attached to a process and we've seen it stop for
> + the first time. If ASYNC_EXEC is true, re-resume threads that
> + should be running. Else if ATTACH, */
> +
Comments are not complete.
> +
> + /* Now go over all threads that are stopped, and print their current
> + frame. If all-stop, then if there's a signalled thread, pick
> + that as current. */
Is it the code you described in the last paragraph of the commit log?
> + ALL_NON_EXITED_THREADS (thread)
> + {
> + struct target_waitstatus *ws;
> +
> + if (first == NULL)
> + first = thread;
> +
> + if (!non_stop)
> + set_running (thread->ptid, 0);
> + else if (thread->state != THREAD_STOPPED)
> + continue;
> +
> + ws = &thread->suspend.waitstatus;
> +
> + if (selected == NULL
> + && thread->suspend.waitstatus_pending_p)
> + selected = thread;
> +
> + if (lowest == NULL || thread->num < lowest->num)
> + lowest = thread;
> +
> + if (non_stop)
> + print_one_stopped_thread (thread);
> + }
> +
> + /* In all-stop, we only print the status of one thread, and leave
> + others with their status pending. */
> + if (!non_stop)
> + {
> + thread = selected;
> + if (thread == NULL)
> + thread = lowest;
> + if (thread == NULL)
> + thread = first;
Looks lowest can't be NULL, so first isn't used.
> +
> + print_one_stopped_thread (thread);
> + }
> +
> + /* For "info program". */
> + thread = inferior_thread ();
> + if (thread->state == THREAD_STOPPED)
> + set_last_target_status (inferior_ptid, thread->suspend.waitstatus);
> }
>
> static void
> @@ -3826,7 +3942,7 @@ remote_start_remote (int from_tty, struct target_ops *target, int extended_p)
> @@ -12936,11 +13040,15 @@ remote_async (struct target_ops *ops, int enable)
> event loop to process them. */
> if (!QUEUE_is_empty (stop_reply_p, stop_reply_queue))
> mark_async_event_handler (remote_async_inferior_event_token);
> + if (target_is_non_stop_p ())
> + mark_async_event_handler (rs->notif_state->get_pending_events_token);
I don't understand why do we need to mark the pending event token.
Previously, we only need to do so when GDB sees a notification.
> }
> else
> {
> serial_async (rs->remote_desc, NULL, NULL);
> clear_async_event_handler (remote_async_inferior_event_token);
> + if (target_is_non_stop_p ())
> + clear_async_event_handler (rs->notif_state->get_pending_events_token);
> }
> }
>
--
Yao (齐尧)
next prev parent reply other threads:[~2015-10-23 15:30 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 15:28 [PATCH 00/18] Remote all-stop on top of non-stop Pedro Alves
2015-10-14 15:28 ` [PATCH 18/18] remote: enable "maint set target-non-stop" by default Pedro Alves
2015-10-14 15:28 ` [PATCH 01/18] Fix mi-nonstop.exp with extended-remote Pedro Alves
2015-10-14 15:28 ` [PATCH 02/18] Remote all-stop-on-top-of-non-stop Pedro Alves
2015-10-24 22:39 ` Yao Qi [this message]
2015-11-23 15:40 ` Pedro Alves
2015-11-23 18:39 ` Pedro Alves
2015-11-26 15:53 ` Yao Qi
2015-10-14 15:28 ` [PATCH 15/18] gdbserver:prepare_access_memory: pick another thread Pedro Alves
2015-10-14 15:28 ` [PATCH 03/18] attach + target always in non-stop mode: stop all threads Pedro Alves
2015-10-26 13:22 ` Yao Qi
2015-11-23 18:15 ` Pedro Alves
2015-11-23 18:42 ` Pedro Alves
2015-11-26 16:12 ` Yao Qi
2015-11-26 16:23 ` Pedro Alves
2015-11-27 9:33 ` Yao Qi
2015-10-14 15:28 ` [PATCH 13/18] infrun: Fix TARGET_WAITKIND_NO_RESUMED handling in non-stop mode Pedro Alves
2015-10-14 15:33 ` [PATCH 05/18] remote: stop reason and watchpoint data address per thread Pedro Alves
2015-10-14 15:33 ` [PATCH 10/18] Remote thread create/exit events Pedro Alves
2015-10-14 16:35 ` Eli Zaretskii
2015-10-26 16:50 ` Yao Qi
2015-11-23 15:41 ` Pedro Alves
2015-12-01 15:12 ` Ulrich Weigand
2015-12-01 16:06 ` Pedro Alves
2015-12-01 17:10 ` Ulrich Weigand
2015-10-14 15:36 ` [PATCH 06/18] New vCtrlC packet, non-stop mode equivalent of \003 Pedro Alves
2015-10-26 14:11 ` Yao Qi
2015-11-30 18:25 ` Pedro Alves
2015-10-14 15:36 ` [PATCH 04/18] gdbserver crash running gdb.threads/non-ldr-exc-1.exp Pedro Alves
2015-10-26 13:54 ` Yao Qi
2015-11-24 16:34 ` Pedro Alves
2015-11-26 16:23 ` Yao Qi
2015-11-30 14:53 ` Pedro Alves
2015-10-14 15:36 ` [PATCH 12/18] testsuite: Range stepping and non-stop mode Pedro Alves
2015-10-14 15:36 ` [PATCH 11/18] gdbserver: fix killed-outside.exp Pedro Alves
2015-10-27 12:02 ` Yao Qi
2015-11-25 15:06 ` Pedro Alves
2015-11-26 16:51 ` Yao Qi
2015-11-26 17:56 ` Pedro Alves
2015-10-14 15:36 ` [PATCH 17/18] gdbserver: don't exit until GDB disconnects Pedro Alves
2015-10-14 15:36 ` [PATCH 14/18] Implement TARGET_WAITKIND_NO_RESUMED in the remote protocol Pedro Alves
2015-10-14 16:36 ` Eli Zaretskii
2015-10-19 16:21 ` Yao Qi
2015-10-19 16:48 ` Pedro Alves
2015-10-14 15:37 ` [PATCH 09/18] Make dprintf-non-stop.exp cope with remote testing Pedro Alves
2015-10-14 15:37 ` [PATCH 07/18] gdbserver crash if gdb attaches too fast Pedro Alves
2015-10-14 15:37 ` [PATCH 16/18] gdbserver/linux: Always wake up event loop after resume Pedro Alves
2015-10-26 17:28 ` Yao Qi
2015-11-25 15:31 ` Pedro Alves
2015-10-14 15:38 ` [PATCH 08/18] gdbserver resume_stop handling bug Pedro Alves
2015-10-14 16:37 ` Eli Zaretskii
2015-11-25 15:12 ` Pedro Alves
2015-11-25 17:53 ` Eli Zaretskii
2015-10-15 10:46 ` [PATCH 00/18] Remote all-stop on top of non-stop Pedro Alves
2015-10-16 16:47 ` Yao Qi
2015-10-19 11:48 ` Yao Qi
2015-10-19 15:28 ` Pedro Alves
2015-10-19 15:47 ` Yao Qi
2015-10-27 13:11 ` Yao Qi
2015-11-30 19:59 ` 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=86vb9x1u2h.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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