[PATCH v2 9/9] gdb: resume ongoing step after handling fork or vfork
Pedro Alves
pedro@palves.net
Thu Mar 31 19:28:13 GMT 2022
On 2022-01-18 04:09, Simon Marchi via Gdb-patches wrote:
> From: Simon Marchi <simon.marchi@efficios.com>
>
> New in v2:
>
> - updated the check in handle_inferior_event from
>
> if (parent->inf->thread_waiting_for_vfork_done != nullptr
> || !switch_back_to_stepped_thread (ecs))
>
> to
>
> if ((!follow_child
> && detach_fork
> && parent->inf->thread_waiting_for_vfork_done != nullptr)
> || !switch_back_to_stepped_thread (ecs))
>
> The `parent` pointer is stale when not following the parent, so that
> broke some follow-fork-mode=child tests. I changed this expression last
> minute before sending and did not re-test :(.
>
OK with the nits I pointed out in v1 addressed.
More information about the Gdb-patches
mailing list