Closed
Description
Debug info is very prone to breakage. We should come up with a way to test it. Maybe look into how LLVM does it.
Metadata
Metadata
Assignees
Labels
Type
Projects
Relationships
Development
No branches or pull requests
Participants
{{ message }}
No one assigned
No type
No projects
None yet
Activity
brson commentedon Apr 12, 2012
One obvious thing is setting up a debuginfo bot that builds everything with debug info, but we need real debuginfo tests too.
graydon commentedon Apr 16, 2012
yeah. there are several tools that know how to dump dwarf to text, and gdb can also be driven by batch input as well as embedded python scripts. this should be very possible.
brson commentedon Feb 12, 2013
@bleibig added support to compiletest for driving gdb and interpreting the results. Considering this done, now let's use it!
Add reftest that checks the layout of repr(int) on non-c-like enums
Add (failing) test to check order of repr(int) enum fields
Add test to check order of repr(int) enum fields
Auto merge of rust-lang#2195 - RalfJung:vtable-validation, r=RalfJung
Clarify the analysis technique used by Kani (rust-lang#2195)