Re: [PATCH v3 2/2] gdb/testsuite: Add gdb.base/memops-watchpoint.exp

[Kevin Buettner <kevinb@redhat.com>]

On Wed, 24 Apr 2024 14:05:31 -0300
Thiago Jung Bauermann <thiago.bauermann@linaro.org> wrote:

> > I also have Fedora 39 (Asahi Remix) running on an M1 macbook.  When
> > I try this test on that machine, I see some timeouts...
> >
> >     (gdb) watch -location a[28]
> >     Hardware watchpoint 2: -location a[28]
> >     (gdb) PASS: gdb.base/memops-watchpoint.exp: set watch on a
> >     watch -location b[28]
> >     Hardware watchpoint 3: -location b[28]
> >     (gdb) PASS: gdb.base/memops-watchpoint.exp: set watchpoint on b
> >     watch -location c[28]
> >     Hardware watchpoint 4: -location c[28]
> >     (gdb) PASS: gdb.base/memops-watchpoint.exp: set watchpoint on c
> >     continue
> >     Continuing.
> >
> >     Hardware watchpoint 2: -location a[28]
> >
> >     Old value = 104 'h'
> >     New value = 0 '\000'
> >     __GI___memset_generic () at ../sysdeps/aarch64/memset.S:67
> >     67		tbz	count, 5, 1f
> >     (gdb) PASS: gdb.base/memops-watchpoint.exp: continue until memset watchpoint hits
> >     continue
> >     Continuing.
> >     FAIL: gdb.base/memops-watchpoint.exp: continue until memcpy watchpoint hits (timeout)
> >     continue
> >     FAIL: gdb.base/memops-watchpoint.exp: continue until memmove watchpoint hits (timeout)
> >     testcase /ironwood1/sourceware-git/macbook-review/bld/../../worktree-review/gdb/testsuite/gdb.base/memops-watchpoint.exp completed in 20 seconds
> >
> > 		    === gdb Summary ===
> >
> >     # of expected passes		4
> >     # of unexpected failures	2
> >
> > Is this demonstrating the bug (31484) ?  
> 
> Hm. Probably. I haven't seen this behaviour in my tests. It's hard to
> say why GDB hung. Can you try to "set debug infrun on" at that point?

I tried running the test again on my macbook and can no longer
reproduce that failure.  I'm seeing 6 passes now.  (No reboots or
updates either. uptime shows that it's been up for 111 days.)

Kevin