llvm-project.git/lldb/test/Shell/ScriptInterpreter/Python, branch users/meinersbur/flang_runtime_split-headers

[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

Reapply "[lldb] Use the function block as a source for function ranges (#117996)"

2024-12-03T10:58:36+00:00

This reverts commit 2526d5b1689389da9b194b5ec2878cfb2f4aca93, reapplying
ba14dac481564000339ba22ab867617590184f4c after fixing the conflict with
 #117532. The change is that Function::GetAddressRanges now recomputes
the returned value instead of returning the member. This means it now
returns a value instead of a reference type.

[lldb] Expose discontinuous functions through SBFunction::GetRanges (#117532)

2024-12-03T09:14:33+00:00

SBFunction::GetEndAddress doesn't really make sense for discontinuous
functions, so I'm declaring it deprecated. GetStartAddress sort of makes
sense, if one uses it to find the functions entry point, so I'm keeping
that undeprecated.

I've made the test a Shell tests because these make it easier to create
discontinuous functions regardless of the host os and architecture. They
do make testing the python API harder, but I think I've managed to come
up with something not entirely unreasonable.

[lldb] Remove lldb-repro utility

2024-10-31T17:39:48+00:00

Remove lldb-repro which was used to run the test suite against a
reproducer. The corresponding functionality has been removed from LLDB
so there's no need for the tool anymore.

Revert "[lldb/crashlog] Make interactive mode the new default" (#96263)

2024-06-21T01:23:50+00:00

Reverts llvm/llvm-project#94575 since introduces test failure:


https://green.lab.llvm.org/job/llvm.org/view/LLDB/job/as-lldb-cmake/6166/

[lldb/crashlog] Make interactive mode the new default (#94575)

2024-06-21T00:23:18+00:00

This patch makes interactive mode as the default when using the crashlog
command. It replaces the existing `-i|--interactive` flag with a new
`-m|--mode` option, that can either be `interactive` or `batch`.

By default, when the option is not explicitely set by the user, the
interactive mode is selected, however, lldb will fallback to batch mode
if the command interpreter is not interactive or if stdout is not a tty.

This also adds some railguards to prevent users from using interactive
only options with the batch mode and updates the tests accordingly.

rdar://97801509

Differential Revision: https://reviews.llvm.org/D141658

Signed-off-by: Med Ismail Bennani