Not a big deal but might be if in the future we had another command starting with br.
I found this because I had an lldbinit that added a breakpad command.
Details
- Reviewers
clayborg JDevlieghere lanza wallace
Diff Detail
- Repository
- rG LLVM Github Monorepo
- Build Status
Buildable 41680 Build 41950: arc lint + arc unit
Event Timeline
We shouldn't be running the test suite that allows your ~/.lldbinit file to be run. This can really hose up many things, so we should change the lldb-vscode test suite to not allow your ~/.lldbinit file to be loaded instead?
Yeah, that's what I do in D70882. I still think tests can be more robust by using explicit lldb command names but don't really care much :). I'm happy to abandon it.
I don't think it is wise to use shortened command names like "br" in a test if you aren't testing shortest command string. We don't guarantee that we will keep all currently unique shortened command names unique in perpetuity...
Sorry for bump to this old diff, but I agree with both Jim and Greg -- we shouldn't be importing your ~/.lldbinit, but tests shouldn't depend on there never being another br s. This change should land as breakpoint set.
lldb/packages/Python/lldbsuite/test/tools/lldb-vscode/launch/TestVSCode_launch.py | ||
---|---|---|
353–354 | we might as well spell this out completely as "breakpoint set" just in case and nothing can currently replace or alias existing commands. |
we might as well spell this out completely as "breakpoint set" just in case and nothing can currently replace or alias existing commands.