From dfa2dcd2f35454e0fccc3ff1462a7646a6e22e5d Mon Sep 17 00:00:00 2001 From: Simon Marchi Date: Wed, 4 May 2022 10:22:56 -0400 Subject: [PATCH] jjb: binutils-gdb: add an expected failure This is a new variant of some other existing expected failure. Change-Id: Ia8d422c525afaed17a33f68000c2ebad2e7c62d3 --- scripts/binutils-gdb/build.sh | 1 + 1 file changed, 1 insertion(+) diff --git a/scripts/binutils-gdb/build.sh b/scripts/binutils-gdb/build.sh index 08671f9..9aa732e 100755 --- a/scripts/binutils-gdb/build.sh +++ b/scripts/binutils-gdb/build.sh @@ -480,6 +480,7 @@ FAIL: gdb.cp/annota3.exp: continue to exit (pattern 4) FAIL: gdb.cp/no-dmgl-verbose.exp: gdb_breakpoint: set breakpoint at 'f(std::string)' FAIL: gdb.gdb/unittest.exp: executable loaded: maintenance selftest, failed none FAIL: gdb.gdb/unittest.exp: no executable loaded: maintenance selftest, failed none +FAIL: gdb.gdb/unittest.exp: reversed initialization: maintenance selftest, failed none FAIL: gdb.mi/mi-exec-run.exp: inferior-tty=separate: mi=separate: force-fail=0: breakpoint hit reported on console (timeout) FAIL: gdb.mi/mi-pending.exp: MI pending breakpoint on mi-pendshr.c:pendfunc2 if x==4 (unexpected output) FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=: action=delete: connection to GDBserver succeeded -- 2.34.1