This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 2/2] Avoid step-over infinite loop in GDBServer
- From: Pedro Alves <palves at redhat dot com>
- To: Antoine Tremblay <antoine dot tremblay at ericsson dot com>, gdb-patches at sourceware dot org
- Date: Fri, 3 Feb 2017 16:21:41 +0000
- Subject: Re: [PATCH 2/2] Avoid step-over infinite loop in GDBServer
- Authentication-results: sourceware.org; auth=none
- References: <20161129120702.9490-1-antoine.tremblay@ericsson.com> <20161129120702.9490-2-antoine.tremblay@ericsson.com>
On 11/29/2016 12:07 PM, Antoine Tremblay wrote:
> - GDBServer stops on instruction A in thread 1.
> - Deletes thread 1 single-step breakpoint.
> - Starts a step-over of thread 1 to step-over the thread 2 breakpoint.
> - GDBServer finishes a step-over and is at instruction B.
> - GDBserver starts a step-over of thread 1 to step-over the thread 3
> breakpoint at instruction B.
> - GDBServer stops on instuction A in thread 1.
> - GDBServer is now in an infinite loop.
This sounds to me very much like a fairness issue. There were
three threads stopped that needed to move past a breakpoint, but
gdbserver always picks thread 1. Why?
Thanks,
Pedro Alves