llvm-project.git/lldb/examples/python, branch users/meinersbur/flang_runtime_split-headers

[lldb] Move the python module import workaround further up

2024-12-07T01:01:58+00:00

[lldb] Add a compiler/interpreter of LLDB data formatter bytecode to examples

2024-12-07T00:27:16+00:00

This PR adds a proof-of-concept for a bytecode designed to ship and
run LLDB data formatters. More motivation and context can be found in
the formatter-bytecode.rst file and on discourse.

https://discourse.llvm.org/t/a-bytecode-for-lldb-data-formatters/82696

Relanding with a fix for a case-sensitive path.

Revert "[lldb] Add a compiler/interpreter of LLDB data formatter bytecode to examples"

2024-12-07T00:26:55+00:00

This reverts commit 60380cd27c6fa5ed6e39866c51b18a64bc4d566a.

[lldb] Add a compiler/interpreter of LLDB data formatter bytecode to examples

2024-12-07T00:10:09+00:00

This PR adds a proof-of-concept for a bytecode designed to ship and
run LLDB data formatters. More motivation and context can be found in
the formatter-bytecode.rst file and on discourse.

https://discourse.llvm.org/t/a-bytecode-for-lldb-data-formatters/82696

Relanding with a fix for a case-sensitive path.

Revert "[lldb] Add a compiler/interpreter of LLDB data formatter bytecode to examples"

2024-12-06T23:34:12+00:00

This reverts commit 7e3da87ca896484a11ac09df297183147154ac91.

I managed to break the bots.

[lldb] Add a compiler/interpreter of LLDB data formatter bytecode to lldb/examples (#113398)

2024-12-06T23:11:21+00:00

This PR adds a proof-of-concept for a bytecode designed to ship and run
LLDB data formatters. More motivation and context can be found in the
`formatter-bytecode.md` file and on discourse.

https://discourse.llvm.org/t/a-bytecode-for-lldb-data-formatters/82696

[lldb] Only run scripted process test on x86_64/arm64

2024-11-15T08:56:34+00:00

The newly added
test/API/functionalities/scripted_process_empty_memory_region/dummy_scripted_process.py
imports
examples/python/templates/scripted_process.py
which only has register definitions for x86_64 and arm64.

Only run this test on those two architectures for now.

Add the ability to define custom completers to the parsed_cmd template. (#109062)

2024-09-24T17:00:00+00:00

If your arguments or option values are of a type that naturally uses one
of our common completion mechanisms, you will get completion for free.
But if you have your own custom values or if you want to do fancy things
like have `break set -s foo.dylib -n ba` only complete on symbols
in foo.dylib, you can use this new mechanism to achieve that.

Add docs and an example use of the scripted command get_flags API. (#109176)

2024-09-19T01:10:43+00:00

The API is present, and we even have a test for it, but it isn't
documented so no one probably knows you can set requirements for your
scripted commands. This just adds docs and uses it appropriately in the
`framestats` example command.

Add the ability for Script based commands to specify their "repeat command" (#94823)

2024-07-03T17:39:34+00:00

Among other things, returning an empty string as the repeat command
disables auto-repeat, which can be useful for state-changing commands.

There's one remaining refinement to this setup, which is that for parsed
script commands, it should be possible to change an option value, or add
a new option value that wasn't originally specified, then ask lldb "make
this back into a command string". That would make doing fancy things
with repeat commands easier.

That capability isn't present in the lldb_private side either, however.
So that's for a next iteration.

I haven't added this to the docs on adding commands yet. I wanted to
make sure this was an acceptable approach before I spend the time to do
that.