[lldb][Windows] Enable the multithreaded and multiple-debuggers API tests (#224305) `api/multithreaded` and `api/multiple-debuggers` build a C++ driver against the SB API. Both were skipped on Windows with `"clang-cl does not support throw or catch (llvm.org/pr24538)"`, which is no longer what stops them. Two things do: the drivers fail to compile because `common.h` and `multi-process-driver.cpp` include `<unistd.h>` unconditionally, and once they compile they run on a different CRT than `liblldb.dll`: the gnu-style clang driver links [`libcmt`](https://github.com/llvm/llvm-project/blob/main/clang/lib/Driver/ToolChains/MSVC.cpp) unless `-fms-runtime-lib=` is passed, so the driver gets the static CRT while `liblldb.dll` gets the DLL one. Fixes: - Include `<direct.h>` and `<io.h>` instead of `<unistd.h>` on Windows, and get the working directory with [`_getcwd`](https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/getcwd-wgetcwd?view=msvc-170). - `get_working_dir` returns a `std::string` now. - `test_stop-hook.cpp` uses `_pipe`/`_fdopen` on Windows, and closes the pipe streams instead of the descriptors they were opened over, write end first so the interpreter's I/O thread sees EOF. - Guard the `<unistd.h>` include in `multi-process-driver.cpp`. - `buildDriver` passes `-fms-runtime-lib=dll` (`dll_dbg` for a Debug build) and drops the `libcmt` the driver adds at the link step. `test_breakpoint_location_callback` stays skipped, for an unrelated reason: `BreakpointCreateByName` with `eFunctionNameTypeFull` resolves no location in a PDB build, while `eFunctionNameTypeAuto` resolves one. Tracked in #224303. rdar://177435499
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.