aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/python-internal.h
diff options
context:
space:
mode:
authorPedro Alves <pedro@palves.net>2025-02-11 14:43:39 +0000
committerPedro Alves <pedro@palves.net>2025-09-23 11:33:17 +0100
commit17956546fd1b7cb4b8bbdceb1c7f4d6f58c891af (patch)
tree541c57fa7a7643db1948ac51b9fe0dccd03dc506 /gdb/python/python-internal.h
parentf0b7e23bdc80d0945517a4390cb56ececa7afc27 (diff)
downloadbinutils-17956546fd1b7cb4b8bbdceb1c7f4d6f58c891af.zip
binutils-17956546fd1b7cb4b8bbdceb1c7f4d6f58c891af.tar.gz
binutils-17956546fd1b7cb4b8bbdceb1c7f4d6f58c891af.tar.bz2
Adjust gdb.base/memops-watchpoint.exp for Cygwin/Windows
When testing gdb.base/memops-watchpoint.exp on Cygwin, I see: ... continue Continuing. Thread 1 "memops-watchpoint" hit Hardware watchpoint 2: -location a[28] Old value = 104 'h' New value = 0 '\000' memset () at /usr/src/debug/cygwin-3.5.4-1/winsup/cygwin/x86_64/memset.S:68 68 rep stosq (gdb) FAIL: gdb.base/memops-watchpoint.exp: continue until memset watchpoint hits Etc. This fails on Windows because there all inferiors are multi-threaded (because both Windows and the Cygwin runtime spawn helper threads), so we always see the 'Thread N "foo" hit' prefix, which the testcase isn't expecting. Fix it by optionally expecting such the "Thread ... hit" prefix bit. Change-Id: Ia06eaf1e152f512f39324d04298e6784eca3e537
Diffstat (limited to 'gdb/python/python-internal.h')
0 files changed, 0 insertions, 0 deletions