Add a breakpoint override resolver feature to lldb (#195392)
This is a general mechanism that allows a custom breakpoint resolver to
"override" the resolver lldb would have used. It is implemented by
making a scripted breakpoint resolver class, implementing an extra
"overrides_resolver" method. When lldb has decided what resolver it is
going to use for the breakpoint, if there are any override resolvers
registered, it will pass the serialized form of the resolver to the
`overrides_resolver` method of the registered resolvers. If any of the
override resolvers return true from the overrides_resolver method, that
resolver will be used in place of the one lldb would have used.
The original motivation for this feature is to make the support of
"debugging a scripting language from the implementation side". We added
the notion of "facade breakpoints" so that a location given in the
context of the scripting language can be handled by the emulation code.
But when you are using lldb in some IDE, when "stopped" in the scripting
language, the IDE will show the scripting language source. It is natural
in that case for the user to expect the UI gesture to set a file and
[8 lines not shown]
Move lldb-python.h to be the first included as its comment demands. (#197048)
The comment was preserved even though the header was almost never
actually placed first. For the most part that didn't matter, but you can
through bad luck uncover the conflict between Python typedefs (in this
case of pid_t) and ones from include/lldb/Host/windows/PosixAPI.h.
So this patch just moves this header to the front in all its
appearances.
Merge tag 'linux_kselftest-kunit-fixes-7.1-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
Pull kunit fixes from Shuah Khan:
"Fix to decouple KUNIT_DEBUGFS and KUNIT_ALL_TESTS options and fix
KUNIT_DEBUGFS dependencies so it depends on DEBUG_FS without which it
will not be useful"
* tag 'linux_kselftest-kunit-fixes-7.1-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest:
kunit: config: KUNIT_DEBUGFS should depend on DEBUG_FS
kunit: config: Enable KUNIT_DEBUGFS by default
[scudo] Add unit tests for common functions
This patch adds unit tests for isPowerOfTwo, computePercentage, and
isAlignedSlow in common_test.cpp. These additions increase the test
coverage for common.h to 100%.
[Clang][CodeGen][NFC] Refactor EmitAsmStmt method (#196885)
Split up massive function into smaller, easier-to-digest chunks.
This places the data into a single structure to limit the amount of
parameters needed per function.
workflows/release-doxygen: Add some security checks and input validation (#196769)
We now ensure the job was started by a release manager before granting
the contents: write permissions and we also validate the input to ensure
it is a proper release string and not something malicious.
[Instrumentor] Add Alloca and Function support; stack usage example
This adds support for alloca instrumentation and function pre/post
instrumentation. Alloca support follows load/store support directly.
Functions require special care to determine the insertion points.
Together, we can showcase how the stack high watermark can be profiled,
see InstrumentorStackUsage.cpp.
WIR [CIR][CodeGen] Remove dead srcAS code in emitCastLValue address spacecast (#197016)
The srcAS variable was computed but never used since upstream's
performAddrSpaceCast only takes (value, destType). Remove the dead code
and its errorNYI for non-target address spaces.
Fixes part of #192314
[CIR] Implement implicit value init for aggregates (#197029)
This implements the AggExprEmitter::VisitImplicitValueInitExpr function
for CIR. The code to emit a zero-initializer was already present. We
just needed to hook it up to the visitor.
[CIR] Implement copy construction of EH catch values (#196419)
This change implements handling of exception variables that require copy
construction (on Itanium targets) before they can be used in a catch
handler, using the cir.contruct_catch_param operation.
Some targets, such as MSABI, do not need to perform an explicit copy.
The construct_catch_param operation is effectively a noop for those
cases and will be lowered as such when the EHABI lowering is implemented
for those targets.
Assisted-by: Cursor / claude-opus-4.7-thinking-xhigh
