Skip to content

Commit baa149b

Browse files
committed
auto merge of #13556 : michaelwoerister/rust/various-fixes, r=alexcrichton
This is a test case verifying that issue #12886 was indeed fixed by PR #13441 from last week. Fixes #12886.
2 parents 72869b6 + 7c042cd commit baa149b

File tree

1 file changed

+35
-0
lines changed

1 file changed

+35
-0
lines changed

Diff for: src/test/debug-info/issue12886.rs

+35
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
// Copyright 2013-2014 The Rust Project Developers. See the COPYRIGHT
2+
// file at the top-level directory of this distribution and at
3+
// http://rust-lang.org/COPYRIGHT.
4+
//
5+
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
6+
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
7+
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
8+
// option. This file may not be copied, modified, or distributed
9+
// except according to those terms.
10+
11+
// ignore-android: FIXME(#10381)
12+
13+
// compile-flags:-g
14+
// debugger:break issue12886.rs:29
15+
// debugger:run
16+
// debugger:next
17+
// check:[...]30[...]s
18+
// debugger:continue
19+
20+
// IF YOU MODIFY THIS FILE, BE CAREFUL TO ADAPT THE LINE NUMBERS IN THE DEBUGGER COMMANDS
21+
22+
// This test makes sure that gdb does not set unwanted breakpoints in inlined functions. If a
23+
// breakpoint existed in unwrap(), then calling `next` would (when stopped at line 27) would stop
24+
// in unwrap() instead of stepping over the function invocation. By making sure that `s` is
25+
// contained in the output, after calling `next` just once, we can be sure that we did not stop in
26+
// unwrap(). (The testing framework doesn't allow for checking that some text is *not* contained in
27+
// the output, which is why we have to make the test in this kind of roundabout way)
28+
fn bar() -> int {
29+
let s = Some(5).unwrap();
30+
s
31+
}
32+
33+
fn main() {
34+
let _ = bar();
35+
}

0 commit comments

Comments
 (0)