[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
show more ...
[lldb] Skip more tests that don't make sense to run remotelySkip another batch of tests that don't really make sense to runremotely.
[lldb] Fix TestStackCorefile.py for ca0ce99fc8
Fix two bugs with stack corefiles patch, restrict test built debugserverThese two tests, TestSkinnyCorefile.py and TestStackCorefile.py,require a new debugserver on darwin systems to run correctly
Fix two bugs with stack corefiles patch, restrict test built debugserverThese two tests, TestSkinnyCorefile.py and TestStackCorefile.py,require a new debugserver on darwin systems to run correctly; for now,skip them if the system debugserver is in use. There's no easy way totest if the debugserver being used supports either of these memoryregion info features. For end users, the fallback will be a fullcorefile and that's not the worst thing, but for the tests it is aproblem.
Add the ability to process save-core stack-memory-only corefilesAdd a field to the qMemoryRegionInfo packet where the remote stubcan describe the type of memory -- heap, stack. Keep track ofmemo
Add the ability to process save-core stack-memory-only corefilesAdd a field to the qMemoryRegionInfo packet where the remote stubcan describe the type of memory -- heap, stack. Keep track ofmemory regions that are stack memory in lldb. Add a new "--stylestack" to process save-core to request that only stack memory beincluded in the corefile.Differential Revision: https://reviews.llvm.org/D107625