[lldb] Remove reproducers documentation
[LLDB][Docs] Indicate `PS1` variable by $
Remove the DarwinLog functionality from debguserverRemove the DarwinLog and qStructuredDataPlugins supportfrom debugserver. The DarwinLog plugin was never debuggedfully and made reliable, and th
Remove the DarwinLog functionality from debguserverRemove the DarwinLog and qStructuredDataPlugins supportfrom debugserver. The DarwinLog plugin was never debuggedfully and made reliable, and the underlying private APIsit uses have migrated since 2016 so none of them existany longer.Differential Revision: https://reviews.llvm.org/D106324rdar://75073283
show more ...
[trace][intel-pt] Create basic SB APIThis adds a basic SB API for creating and stopping traces.Note: This doesn't add any APIs for inspecting individual instructions. That'd be a more complicated
[trace][intel-pt] Create basic SB APIThis adds a basic SB API for creating and stopping traces.Note: This doesn't add any APIs for inspecting individual instructions. That'd be a more complicated change and it might be better to enhande the dump functionality to output the data in binary format. I'll leave that for a later diff.This also enhances the existing tests so that they test the same flow using both the command interface and the SB API.I also did some cleanup of legacy code.Differential Revision: https://reviews.llvm.org/D103500
[lldb] Fix typos. NFC.Differential Revision: https://reviews.llvm.org/D103381
[lldb] Remove references to LLDB_CAPTURE_REPRODUCERRemove the remaining references to LLDB_CAPTURE_REPRODUCER. I removedthe functionality in an earlier commit but forgot that there was acorrespon
[lldb] Remove references to LLDB_CAPTURE_REPRODUCERRemove the remaining references to LLDB_CAPTURE_REPRODUCER. I removedthe functionality in an earlier commit but forgot that there was acorresponding test and logic to unset it in our test suite.
[lldb] Fix typos in documentation (NFC)
[lldb][docs] Use inline literals for code/paths instead of rendering it with the default roleRight now we're using the 'content' role as default which will just renderthese things as cursive (whic
[lldb][docs] Use inline literals for code/paths instead of rendering it with the default roleRight now we're using the 'content' role as default which will just renderthese things as cursive (which isn't really useful for code examples). It alsoprevents us from assigning a more useful default role in the future.
[lldb] Add a "design" section to the documentation.Create a "Design" section for the LLDB documentation. The goal is tohave design documents that describe how the LLDB internals work.Currently s
[lldb] Add a "design" section to the documentation.Create a "Design" section for the LLDB documentation. The goal is tohave design documents that describe how the LLDB internals work.Currently similar pages are mixed together under the "Development". Theexisting pages describing the architecture, the reproducers, thestructured data plugins, and the SB API could be housed here. I hopewe'd see more pages being added here in the future.Differential revision: https://reviews.llvm.org/D88516