[Bug gdb/29729] New: Intermittent failure in gdb.threads/step-N-all-progress.exp

["simark at simark dot ca" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=29729

            Bug ID: 29729
           Summary: Intermittent failure in
                    gdb.threads/step-N-all-progress.exp
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: simark at simark dot ca
  Target Milestone: ---

I get this kind of failures on my CI:

(gdb) PASS: gdb.threads/step-N-all-progress.exp: non-stop=on:
target-non-stop=on: continue to breakpoint: break here
next 3^M
[New Thread 0x7ffff7d88640 (LWP 1327129)]^M
50        return 0;^M
(gdb) [Thread 0x7ffff7d88640 (LWP 1327129) exited]^M
FAIL: gdb.threads/step-N-all-progress.exp: non-stop=on: target-non-stop=on:
next 3 (timeout)

The timeout failure appears to be because the "thread exited" notification was
consumed at the same time of the prompt.  Off-hand, it seems plausible that in
non-stop=on, the event for the non-main thread exit is processed after the
event for the main thread breakpoint hit.  I don't see any way to force it to
go in the "right" order, so I think we'll have to adjust the test to accept
this output.

-- 
You are receiving this mail because:
You are on the CC list for the bug.