rust/tests/ui/runtime/backtrace-debuginfo-aux.rs

//@ run-pass
//@ ignore-test: not a test, used by backtrace-debuginfo.rs to test file!()

#[inline(never)]
pub fn callback<F>(f: F) where F: FnOnce((&'static str, u32)) {
    f((file!(), line!()))
}

// We emit the wrong location for the caller here when inlined on MSVC
#[cfg_attr(not(target_env = "msvc"), inline(always))]
#[cfg_attr(target_env = "msvc", inline(never))]
pub fn callback_inlined<F>(f: F) where F: FnOnce((&'static str, u32)) {
    f((file!(), line!()))
}
tests: Add missing run-pass annotations 2019-07-26 16:54:25 -05:00			`//@ run-pass`
std: Include line numbers in backtraces. Fixes #20978 for supported platforms (i.e. non-Android POSIX). This uses `backtrace_pcinfo` to inspect the DWARF debug info and list the file and line pairs for given stack frame. Such pair is not unique due to the presence of inlined functions and the updated routine correctly handles this case. The code is modelled after libbacktrace's `backtrace_full` routine. There is one known issue with this approach. Macros, when invoked, take over the current frame and shadows the file and line pair which has invoked a macro. In particular, this makes many panicking macros a bit harder to inspect. This really is a debuginfo problem, and the backtrace routine should print them correctly with a correct debuginfo. 2015-02-26 10:12:22 -06:00			`//@ ignore-test: not a test, used by backtrace-debuginfo.rs to test file!()`

			`#[inline(never)]`
			`pub fn callback<F>(f: F) where F: FnOnce((&'static str, u32)) {`
			`f((file!(), line!()))`
			`}`

Print inlined functions on Windows 2017-11-15 11:01:09 -06:00			`// We emit the wrong location for the caller here when inlined on MSVC`
Add line numbers to MSVC backtrace Add comments 2015-09-04 17:17:16 -05:00			`#[cfg_attr(not(target_env = "msvc"), inline(always))]`
			`#[cfg_attr(target_env = "msvc", inline(never))]`
std: Include line numbers in backtraces. Fixes #20978 for supported platforms (i.e. non-Android POSIX). This uses `backtrace_pcinfo` to inspect the DWARF debug info and list the file and line pairs for given stack frame. Such pair is not unique due to the presence of inlined functions and the updated routine correctly handles this case. The code is modelled after libbacktrace's `backtrace_full` routine. There is one known issue with this approach. Macros, when invoked, take over the current frame and shadows the file and line pair which has invoked a macro. In particular, this makes many panicking macros a bit harder to inspect. This really is a debuginfo problem, and the backtrace routine should print them correctly with a correct debuginfo. 2015-02-26 10:12:22 -06:00			`pub fn callback_inlined<F>(f: F) where F: FnOnce((&'static str, u32)) {`
			`f((file!(), line!()))`
			`}`