rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2016-10-31	adapt debuginfo tests for gdb with native rust support	Tim Neumann	-3/+6

2015-09-19	Feature-gate `#[no_debug]` and `#[omit_gdb_pretty_printer_section]`	Andrew Paseltiner	-0/+1
	Closes #28091.
2015-03-26	Mass rename uint/int to usize/isize	Alex Crichton	-4/+4
	Now that support has been removed, all lingering use cases are renamed.
2015-02-10	Enable test/debuginfo on android	Eunji Jeong	-1/+0

2014-12-30	debuginfo: Add a rust-gdb shell script that will start GDB with Rust pretty ↵	Michael Woerister	-0/+1
	printers enabled.
2014-10-31	debuginfo: Make GDB tests use line breakpoints like done in LLDB tests.	Michael Woerister	-2/+0
	On some Windows versions of GDB this is more stable than setting breakpoints via function names.
2014-10-28	Update code with new lint names	Aaron Turon	-1/+1

2014-10-22	debuginfo: Gate all LLDB debuginfo tests on a minimum LLDB version being ↵	Michael Woerister	-0/+1
	available
2014-09-25	debuginfo: Make sure that all calls to drop glue are associated with debug ↵	Michael Woerister	-2/+2
	locations. This commit makes rustc emit debug locations for all call and invoke statements in LLVM IR, if they are contained within a function that debuginfo is enabled for. This is important because LLVM does not handle the case where a function body containing debuginfo is inlined into another function with debuginfo, but the inlined call statement does not have a debug location. In this case, LLVM will not know where (in terms of source code coordinates) the function was inlined to and we end up with some statements still linked to the source locations in there original, non-inlined function without any indication that they are indeed an inline-copy. Later, when generating DWARF from the IR, LLVM will interpret this as corrupt IR and abort. Unfortunately, the undesirable case described above can still occur when using LTO. If there is a crate compiled without debuginfo calling into a crate compiled with debuginfo, we again end up with the conditions triggering the error. This is why some LTO tests still fail with the dreaded assertion, if the standard library was built with debuginfo enabled. That is, `RUSTFLAGS_STAGE2=-g make rustc-stage2` will succeed but `RUSTFLAGS_STAGE2=-g make check` will still fail after this commit has been merged. This is a problem that has to be dealt with separately. Fixes #17201 Fixes #15816 Fixes #15156
2014-07-16	debuginfo: Add LLDB autotests to debuginfo test suite.	Michael Woerister	-1/+52
	This commit adds LLDB autotests to the test suite but does not activate them by default yet.
2014-05-07	debuginfo: Split debuginfo autotests into debuginfo-gdb and debuginfo-lldb	Michael Woerister	-0/+109