Repository navigation
debuginfo-gdb tests can't handle new gdb that supports rust #36323
Description
Activity
@brson @alexcrichton We need test infrastructure that uses a Rust-enabled version of GDB.
set language rustmight be necessary in those tests?Discussed during tools triage today, conclusions were:
- Ideally tests would support all versions of GDB, perhaps even including a gdb/lldb style split of assertions and commands for newer versions of GDB
- We should have bots testing both versions of GDB
- This may involve two bots with two versions of GDB
- It may also involve one bot testing two versions of GDB
This is an example of a failure, which also makes it quite obvious why the tests fail:
error: line not found in debugger output: $4 = {a = 3, b = 4, c = 5, d = 6, e = 7, f = 8, g = 9, h = 10} <snip> $4 = function_arg_initialization::BigStruct {a: 3, b: 4, c: 5, d: 6, e: 7, f: 8, g: 9, h: 10}This is a very nasty failure case because I haven’t seen a successful run of tests on arch for months now.
Yes, I think this can be considered fixed.
Lots of
error: line not found in debugger outpute.g. see buildlog for 1.13.0~~nightly.20160904, shorter snippet of one failure: https://paste.debian.net/812883/