| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-07-27 | tests: Move run-pass tests without naming conflicts to ui | Vadim Petrochenkov | -14/+0 | |
| 2019-07-27 | tests: Add missing run-pass annotations | Vadim Petrochenkov | -0/+1 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -10/+0 | |
| 2018-01-26 | Print inlined functions on Windows | John Kåre Alsaker | -3/+1 | |
| 2017-07-23 | Fix some doc/comment typos. | Bruce Mitchener | -1/+1 | |
| 2016-04-11 | tests: update for MIR debuginfo. | Eduard Burtescu | -2/+0 | |
| 2016-03-17 | Add #[rustc_no_mir] to make tests pass with -Z orbit. | Eduard Burtescu | -0/+2 | |
| 2015-09-05 | Add line numbers to MSVC backtrace | Diggory Blake | -1/+5 | |
| Add comments | ||||
| 2015-03-15 | Strip all leading/trailing newlines | Tamir Duberstein | -1/+0 | |
| 2015-02-27 | std: Include line numbers in backtraces. | Kang Seonghoon | -0/+22 | |
| 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. | ||||
