Go to file
Michael Stone d0415e5734 vscode-extensions.vadimcn.vscode-lldb: fix on Darwin
Summary:

  vscode-lldb has been broken on Darwin due to a build-time issue:

    * on Darwin, the vscode-lldb build scripts expect $HOME to exist and be
      writable, #202507

  and several runtime-issues:

    * codelldb can't find its dynamic libraries (#160874)

    * lldb-server from nixpkgs doesn't work due to missing the

        "com.apple.security.cs.debugger"

      macOS codesigning entitlement, (#38624), also with the symptom that
      tccd, the macOS "Transparency, Consent, and Control" daemon, denies
      requests it receives from vscode/codium with log messages like:

	  "AUTHREQ_CTX: msgID=..., function=<private>, service=kTCCServiceDeveloperTool, preflight=yes, query=1,"
          "Service kTCCServiceDeveloperTool does not allow prompting; returning denied."
          "AUTHREQ_RESULT: msgID=..., authValue=0, authReason=5, authVersion=1, error=(null),", etc.

    * lldb-server from nixpkgs may also provide a different CLI interface than
      codelldb expects on macOS.

    * vscode-lldb directs lldb to load rust pretty-printing scripts which need
      to be preserved through the build process in nixpkgs

Solution:

  * The build problem can be fixed by setting HOME="$(pwd)/home", as suggested
    in #202507.

  * The dynamic libraries issue can be fixed by setting LD_LIBRARY_PATH while
    wrapping codelldb

  * The permissions issue and CLI interface issue can both be fixed by using
    Xcode's debugserver,

      /Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Versions/A/Resources/debugserver

    on macOS, since it has the required entitlement and the expected interface.

  * Finally, the script-loading issue can be fixed by copying the required
    scripts to the location that vscode-lldb expects to find them in.

Fixes:

  * #148946: Error failed to get reply to handshake packet on x86_64-darwin
    with vscode-extensions.vadimcn.vscode-lldb

  * #160874: codelldb inside of vscode-lldb extension doesn't work

  * #202507: vscode-extensions.vadimcn.vscode-lldb fails to build on aarch64-darwin
2024-04-10 11:08:45 +02:00
.github ci: fix the branch patterns of the 'Check cherry-picks' action 2024-04-09 19:27:11 +02:00
doc doc/stdenv: document prefixKey more precisely (#302535) 2024-04-08 14:07:40 +02:00
lib Merge pull request #284551 from hercules-ci/types-attrTag 2024-04-09 20:48:44 +02:00
maintainers Merge pull request #303028 from annaleaves/removeannannalee 2024-04-10 14:52:18 +08:00
nixos Merge pull request #297640 from Mic92/digitalocean 2024-04-10 09:08:20 +02:00
pkgs vscode-extensions.vadimcn.vscode-lldb: fix on Darwin 2024-04-10 11:08:45 +02:00
.editorconfig Merge pull request #288812 from hercules-ci/lib-flake-version 2024-03-03 18:19:00 +01:00
.git-blame-ignore-revs git-blame-ignore-revs: ignore CUDA-related reformatting 2024-04-01 01:14:31 +00:00
.gitattributes
.gitignore Merge pull request #263348 from chayleaf/redundant-result 2024-03-11 11:44:37 +01:00
.mailmap maintainers: stepbrobd change email and fingerprint 2023-12-06 13:07:16 -05:00
.version .version: Make lib/.version source of truth 2024-02-26 22:34:10 +01:00
CONTRIBUTING.md treewide: Switch markdown placeholder from "..." to <...> 2024-03-28 09:28:12 +01:00
COPYING COPYING: 2023 -> 2024 2024-01-30 16:49:51 +01:00
default.nix
flake.nix nixos/flake: put nixpkgs in NIX_PATH and system registry for flake configs 2024-02-03 20:44:38 -08:00
README.md README.md: fix broken images 2024-04-03 09:11:04 -07:00

NixOS logo

Contributors badge Open Collective supporters

Nixpkgs is a collection of over 80,000 software packages that can be installed with the Nix package manager. It also implements NixOS, a purely-functional Linux distribution.

Manuals

  • NixOS Manual - how to install, configure, and maintain a purely-functional Linux distribution
  • Nixpkgs Manual - contributing to Nixpkgs and using programming-language-specific Nix expressions
  • Nix Package Manager Manual - how to write Nix expressions (programs), and how to use Nix command line tools

Community

Other Project Repositories

The sources of all official Nix-related projects are in the NixOS organization on GitHub. Here are some of the main ones:

  • Nix - the purely functional package manager
  • NixOps - the tool to remotely deploy NixOS machines
  • nixos-hardware - NixOS profiles to optimize settings for different hardware
  • Nix RFCs - the formal process for making substantial changes to the community
  • NixOS homepage - the NixOS.org website
  • hydra - our continuous integration system
  • NixOS Artwork - NixOS artwork

Continuous Integration and Distribution

Nixpkgs and NixOS are built and tested by our continuous integration system, Hydra.

Artifacts successfully built with Hydra are published to cache at https://cache.nixos.org/. When successful build and test criteria are met, the Nixpkgs expressions are distributed via Nix channels.

Contributing

Nixpkgs is among the most active projects on GitHub. While thousands of open issues and pull requests might seem a lot at first, it helps consider it in the context of the scope of the project. Nixpkgs describes how to build tens of thousands of pieces of software and implements a Linux distribution. The GitHub Insights page gives a sense of the project activity.

Community contributions are always welcome through GitHub Issues and Pull Requests.

For more information about contributing to the project, please visit the contributing page.

Donations

The infrastructure for NixOS and related projects is maintained by a nonprofit organization, the NixOS Foundation. To ensure the continuity and expansion of the NixOS infrastructure, we are looking for donations to our organization.

You can donate to the NixOS foundation through SEPA bank transfers or by using Open Collective:

License

Nixpkgs is licensed under the MIT License.

Note: MIT license does not apply to the packages built by Nixpkgs, merely to the files in this repository (the Nix expressions, build scripts, NixOS modules, etc.). It also might not apply to patches included in Nixpkgs, which may be derivative works of the packages to which they apply. The aforementioned artifacts are all covered by the licenses of the respective packages.