Re: [PATCH 0/8] Break at each iteration for breakpoints placed on a while statement

[Luis Machado <lgustavo at codesourcery dot com>]

On 04/04/2016 10:56 AM, Yao Qi wrote:
> Kevin Buettner <kevinb@redhat.com> writes:
>
> > This patch set changes the current behavior of breakpoints placed on
> > while loops. (It actually restores past behavior; see below.)
>
> Hi Pedro,
> your recent change https://sourceware.org/ml/gdb-patches/2016-03/msg00462.html
> triggers a test failure in gdb.base/jit.exp on arm-linux that breakpoint
> on the loop "WAIT_FOR_GDB" isn't hit.  The problem is also found by
> buildbot, https://sourceware.org/ml/gdb-testers/2016-q1/msg10203.html
>
> The problem is what this patch series is trying to fix, so I think we
> do need this patch series.  Do you plan to review them? (I ask you this
> because you gave comments to one of these patches) or I can review
> them if you don't have cycles.

Thinking about the series, isn't this problem related to the compiler 
optimizing things and/or presenting an imprecise addr/line information 
as opposed to GDB doing the wrong thing.

Just wondering if working around the compiler is the best choice or if 
we risk breaking something else depending on the way code is output in 
some cases.