This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 3/7] range stepping: gdbserver on x86/linux
- From: Yao Qi <yao at codesourcery dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Wed, 15 May 2013 15:40:59 +0800
- Subject: Re: [PATCH 3/7] range stepping: gdbserver on x86/linux
- References: <1363006291-13334-1-git-send-email-yao at codesourcery dot com> <1363006291-13334-4-git-send-email-yao at codesourcery dot com> <519282CB dot 4030800 at redhat dot com>
On 05/15/2013 02:30 AM, Pedro Alves wrote:
- it assumes GDB will ever only send one r action per vCont. I'd much
rather we don't bake in that assumption.
I am afraid not. It works for multiple r actions in one vCont.
- It seems like this leaves threads with stale step ranges. Because
linux-low.c only clears the stepping range of the thread that is reporting
the event (here):
OK. Looks we need to call thread_clear_range_stepping for the thread we
parsed in handle_v_cont first.
--
Yao (éå)