This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v3 10/17] Implement all-stop on top of a target running non-stop mode
- From: Yao Qi <qiyaoltc at gmail dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: Yao Qi <qiyaoltc at gmail dot com>, gdb-patches at sourceware dot org
- Date: Thu, 21 May 2015 10:17:49 +0100
- Subject: Re: [PATCH v3 10/17] Implement all-stop on top of a target running non-stop mode
- Authentication-results: sourceware.org; auth=none
- References: <1429267521-21047-1-git-send-email-palves at redhat dot com> <1429267521-21047-11-git-send-email-palves at redhat dot com> <86a8y1zqkd dot fsf at gmail dot com> <5538017B dot 9040907 at redhat dot com> <86h9s6x9eo dot fsf at gmail dot com> <555B7C14 dot 1020504 at redhat dot com>
Pedro Alves <palves@redhat.com> writes:
> So the only difference between stepping over a breakpoint in-line or
> out-of-line here, is that with the former, threads had been previously
> paused, so we re-resume them while the signal handler runs (to avoid
> debugger-induced inferior deadlock).
Looks in-line stepping and out-of-line stepping behaves similarly under
this context.
>
> Let me know if that answered your question.
Yes, that is what I want to know, thanks.
--
Yao (éå)