1 files changed, 0 insertions, 30 deletions
diff --git a/src/test/debuginfo/issue-12886.rs b/src/test/debuginfo/issue-12886.rs
deleted file mode 100644
index 389221cbb..000000000
--- a/src/test/debuginfo/issue-12886.rs
+++ /dev/null
@@ -1,30 +0,0 @@
-// ignore-windows failing on 64-bit bots FIXME #17638
-// ignore-lldb
-// ignore-aarch64
-
-// compile-flags:-g
-
-// gdb-command:run
-// gdb-command:next
-// gdb-check:[...]24[...]let s = Some(5).unwrap(); // #break
-// gdb-command:continue
-
-#![feature(omit_gdb_pretty_printer_section)]
-#![omit_gdb_pretty_printer_section]
-
-// IF YOU MODIFY THIS FILE, BE CAREFUL TO ADAPT THE LINE NUMBERS IN THE DEBUGGER COMMANDS
-
-// This test makes sure that gdb does not set unwanted breakpoints in inlined functions. If a
-// breakpoint existed in unwrap(), then calling `next` would (when stopped at `let s = ...`) stop
-// in unwrap() instead of stepping over the function invocation. By making sure that `s` is
-// contained in the output, after calling `next` just once, we can be sure that we did not stop in
-// unwrap(). (The testing framework doesn't allow for checking that some text is *not* contained in
-// the output, which is why we have to make the test in this kind of roundabout way)
-fn bar() -> isize {
-    let s = Some(5).unwrap(); // #break
-    s
-}
-
-fn main() {
-    let _ = bar();
-}