[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/Core] Fix "sticky" long progress messagesWhen the terminal window is too small, lldb would wrap progress messagesaccross multiple lines which would break the progress event handlingcode tha
[lldb/Core] Fix "sticky" long progress messagesWhen the terminal window is too small, lldb would wrap progress messagesaccross multiple lines which would break the progress event handlingcode that is supposed to clear the message once the progress is completed.This causes the progress message to remain on the screen, sometimes partially,which can be confusing for the user.To fix this issue, this patch trims the progress message to the terminalwidth taking into account the progress counter leading the message forfinite progress events and also the trailing `...`.rdar://91993836Differential Revision: https://reviews.llvm.org/D124785Signed-off-by: Med Ismail Bennani <[email protected]>
[lldb/test] Add events listener helper function to lldbtestThis patch introduces 2 new lldb utility functions:- lldbutil.start_listening_from: This can be called in the test setup to create a li
[lldb/test] Add events listener helper function to lldbtestThis patch introduces 2 new lldb utility functions:- lldbutil.start_listening_from: This can be called in the test setup to create a listener and set it up for a specific event mask and add it to the user-provided broadcaster's list.- lldbutil.fetch_next_event: This will use fetch a single event from the provided istener and return it if it matches the provided broadcaster.The motivation behind this is to easily test new kinds of events(i.e. Swift type-system progress events). However, this patch alsoupdates `TestProgressReporting.py` and `TestDiagnosticReporting.py`to make use of these new helper functions.Differential Revision: https://reviews.llvm.org/D122193Signed-off-by: Med Ismail Bennani <[email protected]>
Revert "[lldb/test] Add events listener helper class to lldbtest"It removes the "wait-until-event-thread-stops" logic, which makesTestDiagnosticReporting.py flaky.This reverts commits 09ff41a087
Revert "[lldb/test] Add events listener helper class to lldbtest"It removes the "wait-until-event-thread-stops" logic, which makesTestDiagnosticReporting.py flaky.This reverts commits 09ff41a087760ea7e80b8e5390a05101c5a5b929 andacdd41b4590935e39208a941fbac7889d778e8e5.
[lldb/test] Add events listener helper class to lldbtestThis patch introduces a generic helper class that will listen forevent in a background thread and match it against a source broadcaster.If
[lldb/test] Add events listener helper class to lldbtestThis patch introduces a generic helper class that will listen forevent in a background thread and match it against a source broadcaster.If the event received matches the source broadcaster, the event isqueued up in a list that the user can access later on.The motivation behind this is to easily test new kinds of events(i.e. Swift type-system progress events). However, this patch alsoupdates `TestProgressReporting.py` and `TestDiagnosticReporting.py`to make use of this new helper class.Differential Revision: https://reviews.llvm.org/D121977Signed-off-by: Med Ismail Bennani <[email protected]>
Reland "[lldb/test] Fix TestProgressReporting.py race issue with the event listener"This patch relands commit 3e3e79a9e4c378b59f5f393f556e6a84edcd8898, andfixes the memory sanitizer issue describe
Reland "[lldb/test] Fix TestProgressReporting.py race issue with the event listener"This patch relands commit 3e3e79a9e4c378b59f5f393f556e6a84edcd8898, andfixes the memory sanitizer issue described in D120284, by removing theoutput arguments from the LLDB_INSTRUMENT_VA invocation.Differential Revision: https://reviews.llvm.org/D120599Signed-off-by: Med Ismail Bennani <[email protected]>
Revert "[lldb/test] Fix TestProgressReporting.py race issue with the event listener"This reverts commit 3e3e79a9e4c378b59f5f393f556e6a84edcd8898.MemorySanitizer: use-of-uninitialized-value
[lldb/test] Fix TestProgressReporting.py race issue with the event listenerThis patch is a follow-up of D120100 to address some feedbacks from@labath.This should mainly fix the race issue with t
[lldb/test] Fix TestProgressReporting.py race issue with the event listenerThis patch is a follow-up of D120100 to address some feedbacks from@labath.This should mainly fix the race issue with the even listener by movingthe listener setup to the main thread.This also changes the SBDebugger::GetProgressFromEvent SWIG bindingarguments to be output only, so the user don't have to provide them.Finally, this updates the test to check it the out arguments are returnedin a tuple and re-enables the test on all platforms.Differential Revision: https://reviews.llvm.org/D120284Signed-off-by: Med Ismail Bennani <[email protected]>
[lldb/bindings] Expose the progress reporting machinery to the SWIG interfaceThis patch defines the SBDebugger::eBroadcastBitProgress enum in the SWIGinterface and exposes the SBDebugger::{GetProg
[lldb/bindings] Expose the progress reporting machinery to the SWIG interfaceThis patch defines the SBDebugger::eBroadcastBitProgress enum in the SWIGinterface and exposes the SBDebugger::{GetProgressFromEvent,GetBroadcaster}methods as well.This allows to exercise the API from the script interpreter using python.Differential Revision: https://reviews.llvm.org/D120100Signed-off-by: Med Ismail Bennani <[email protected]>