From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/7] Replace "struct continuation" mechanism by something more extensible
Date: Tue, 18 Aug 2015 12:50:00 -0000 [thread overview]
Message-ID: <86h9nw3gmp.fsf@gmail.com> (raw)
In-Reply-To: <1439398917-22761-3-git-send-email-palves@redhat.com> (Pedro Alves's message of "Wed, 12 Aug 2015 18:01:52 +0100")
Pedro Alves <palves@redhat.com> writes:
> (tui_init): Install tui_on_normal_stop as normal_stop
> * observer.
>
Remove *.
> +
> +/* Prepare for a step/next/etc. command. Any target resource
> + allocated here is undone in the FSM's clean_up method. */
> +
> +static void
> +step_command_fsm_prepare (struct step_command_fsm *sm,
> + int skip_subroutines, int single_inst,
> + int count, int thread)
> +{
> + struct thread_info *tp = inferior_thread ();
Nit: get thread_info by THREAD rather than inferior_thread ()?
> +
> +/* Implementation of the 'should_stop' FSM method for the finish
> + commands. Detects whether the thread stepped out of the function
> + successfully, and if so, captures the function's return value and
> + marks the FSM finished. */
> +
> +static int
> +finish_command_fsm_should_stop (struct thread_fsm *self)
> {
> - struct finish_command_continuation_args *a = arg;
> + struct finish_command_fsm *f = (struct finish_command_fsm *) self;
> + struct return_value_info *rv = &f->return_value;
> + struct thread_info *tp = inferior_thread ();
Nit: Get TP from f->thread rather than inferior_thread ()?
--
Yao (齐尧)
next prev parent reply other threads:[~2015-08-18 12:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 17:02 [PATCH 0/7] Replace continuations with an extendable "class" Pedro Alves
2015-08-12 17:02 ` [PATCH 3/7] Convert infcalls to thread_fsm mechanism Pedro Alves
2015-08-12 17:02 ` [PATCH 2/7] Replace "struct continuation" mechanism by something more extensible Pedro Alves
2015-08-18 12:50 ` Yao Qi [this message]
2015-08-19 14:55 ` Pedro Alves
2015-08-12 17:02 ` [PATCH 1/7] Merge async and sync code paths some more Pedro Alves
2015-08-12 19:48 ` Simon Marchi
2015-08-17 17:54 ` Pedro Alves
2015-08-17 19:28 ` Simon Marchi
2015-08-18 10:48 ` Yao Qi
2015-08-19 14:11 ` Pedro Alves
2015-08-27 13:26 ` Yao Qi
2015-10-16 0:35 ` Joel Brobecker
2015-10-16 12:24 ` Pedro Alves
2015-10-16 16:22 ` Joel Brobecker
2015-10-16 16:37 ` Pedro Alves
2015-10-16 17:05 ` Joel Brobecker
2015-10-22 16:18 ` Pedro Alves
2015-08-12 17:02 ` [PATCH 4/7] Convert the until/advance commands to thread_fsm mechanism Pedro Alves
2015-08-12 17:11 ` [PATCH 6/7] Garbage collect thread continuations Pedro Alves
2015-08-12 17:11 ` [PATCH 7/7] Delete enum inferior_event_handler::INF_TIMER Pedro Alves
2015-08-18 11:22 ` Yao Qi
2015-08-12 17:11 ` [PATCH 5/7] Garbage collect dummy_frame_ctx_saver Pedro Alves
2015-08-18 12:52 ` [PATCH 0/7] Replace continuations with an extendable "class" Yao Qi
2015-08-19 14:56 ` Pedro Alves
2015-09-09 17:33 ` 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=86h9nw3gmp.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