[lldb][Module] Don't try to locate scripting resources without a ScriptInterpreter (#187091) I'm in the process of moving `SanitizedScriptingModuleName` into `ScriptInterpreter` as a `virtual` API. The nullptr check inside the constructor made that more difficult because it implied we may not have a `ScriptInterpreter` available to call the sanitization API on. Really the `nullptr` check is redundant because even if we succesfully sanitize and then locate some scripts, `Module::LoadScriptingResourceInTarget` bails out if we don't have a `ScriptInterpreter`. This patch moves the early exit in `LoadScriptingResourceInTarget` to before we make the call to `LocateExecutableScriptingResources`. That way we ensure we never get to `SanitizedScriptingModuleName` without a valid `ScriptInterpreter`.
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.