Have CommandObjectParsed check for "commands that take no arguments".This is currently being done in an ad hoc way, and so for somecommands it isn't being checked. We have the info to make this c
Have CommandObjectParsed check for "commands that take no arguments".This is currently being done in an ad hoc way, and so for somecommands it isn't being checked. We have the info to make this check,since commands are supposed to add their arguments to the m_argumentsfield of the CommandObject. This change uses that info to check whetherthe command received arguments in error.A handful of commands weren't defining their argument types, I also hadto fix them. And a bunch of commands were checking for arguments byhand, so I removed those checks in favor of the CommandObject one. Thatalso meant I had to change some tests that were checking for the ad hocerror outputs.Differential Revision: https://reviews.llvm.org/D128453
show more ...
[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://r
[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://reviews.llvm.org/D128077
[lldb] Allow dumping the state of all scratch TypeSystemsThis adds the `target dump typesystem'`command which dumps the TypeSystem of thetarget itself (aka the 'scratch TypeSystem'). This is simil
[lldb] Allow dumping the state of all scratch TypeSystemsThis adds the `target dump typesystem'`command which dumps the TypeSystem of thetarget itself (aka the 'scratch TypeSystem'). This is similar to `target modulesdump ast` which dumps the AST of lldb::Modules associated with a selectedtarget.Unlike `target modules dump ast`, the new command is not a subcommand of `targetmodules dump` as it's not touching the modules of a target at all. Also unlike`target modules dump ast` I tried to keep the implementation language-neutral,so this patch moves our Clang `Dump` to the `TypeSystem` interface so it willalso dump the state of any future/downstream scratch TypeSystems (e.g., Swift).That's also why the command just refers to a 'typesystem' instead of an 'ast'(which is only how Clang is necessarily modelling the internal TypeSystemstate).The main motivation for this patch is that I need to write some tests that checkfor duplicates in the ScratchTypeSystemClang of a target. There is currently noway to check for this at the moment (beside measuring memory consumption ofcourse). It's probably also useful for debugging LLDB itself.Reviewed By: labathDifferential Revision: https://reviews.llvm.org/D111936