This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/9 V3] Use reinsert breakpoint for vCont;s
- From: Pedro Alves <palves at redhat dot com>
- To: Antoine Tremblay <antoine dot tremblay at ericsson dot com>, Yao Qi <qiyaoltc at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 25 Nov 2016 13:44:15 +0000
- Subject: Re: [PATCH 0/9 V3] Use reinsert breakpoint for vCont;s
- Authentication-results: sourceware.org; auth=none
- References: <1467295765-3457-1-git-send-email-yao.qi@linaro.org> <wwok4m39swrb.fsf@ericsson.com> <20161121120822.GA28605@E107787-LIN> <wwok37ikrgmq.fsf@ericsson.com> <20161124215510.pbsobdtj6niycjhd@localhost> <wwokshqfycjw.fsf@ericsson.com> <wwokr35zya7o.fsf@ericsson.com>
I'm behind on this whole discussion, but, the comment below
caught my attention:
On 11/25/2016 01:12 PM, Antoine Tremblay wrote:
> In fact thinking more about this we may need to remove all breakpoints
> at any pc since get_next_pc may read memory in other places then the
> current pc to deal with atomic sequences for example or for other
> instructions too.
>
> If it reads a breakpoint in memory there it may come-up with an invalid
> next pc.
How can that happen, given gdbserver's memory read routine takes
share to hide breakpoint breakpoints?
I.e., read_inferior_memory -> check_mem_read.
Thanks,
Pedro Alves