debuginfo: Add LLDB autotests without activating them yet #15573
+3,569
−265
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The shutdown call would always result in an exception being printed to standard error.
This commit adds LLDB autotests to the test suite but does not activate them by default yet.
Some older versions of LLDB have problems with multiple instances running in parallel. This commit makes sure we don't do that.
|
I fixed the gdb test case and rebased. I'll have bors give it another try. |
|
@alexcrichton Will bors pick this up even if building failed on Travis CI? The failure there just seems to be some timeout problem... |
|
It should yeah, I gave it another r+ to see what happens |
bors
added a commit
that referenced
this pull request
Jul 16, 2014
…l, r=alexcrichton This PR adds the LLDB autotests to the debuginfo test suite so I don't have to keep rebasing them locally. They are still disabled by default in `tests.mk`. One of the commits also contains a Python pretty printer which can make LLDB print values with Rust syntax. This was mainly added to deal with output format differences between LLDB versions but you can also use it for your normal LLDB debugging sessions. ``` // The following LLDB commands will load and activate the Rust printers command script import ./src/etc/lldb_rust_formatters.py type summary add --no-value --python-function lldb_rust_formatters.print_val -x .* --category Rust type category enable Rust ``` Expect some rough edges with these, they have not been tested apart from there use in the autotests...
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Sep 18, 2023
assist : `into_to_qualified_from` fixes rust-lang#15539. This assist converts an `.into()` call into an explicit fully qualified `from()` call.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the LLDB autotests to the debuginfo test suite so I don't have to keep rebasing them locally. They are still disabled by default in
tests.mk. One of the commits also contains a Python pretty printer which can make LLDB print values with Rust syntax. This was mainly added to deal with output format differences between LLDB versions but you can also use it for your normal LLDB debugging sessions.Expect some rough edges with these, they have not been tested apart from there use in the autotests...