Environment variables don't work with LLDB #191

NewProggie · 2016-08-31T19:42:38Z

Hey,

in order to debug my executable, I need to pass an environment variable to the debugger. On console this would be something like:

$ lldb ./my_executable
(lldb) env DYLD_LIBRARY_PATH=/my/foo/bar
(lldb) run

I already tried configuring launch.jsonwith "setupCommands": [{"text": "env DYLD_LIBRARY_PATH=/my/foo/bar"}] and "customLaunchSetupCommands": [{"text": "process launch -v DYLD_LIBRARY_PATH=/my/foo/bar"}] of which neither seem to work. Unfortunately, I don't get any specific error messages other than that the lldb process returned some error.
Configuring the environment variable in tasks.json to include those variables doesn't work either.

Second, is there a way to get more debugging information from the debugger? The only information I'm currently getting is that lldb returned some malformed information, but not any details.

Edit: I'm using OS X 10.11.6 with VS Code version 1.4.0.

The text was updated successfully, but these errors were encountered:

paulmaybee · 2016-08-31T20:01:40Z

Did you mean "configuring the environment variable in launch.json ..."?

NewProggie · 2016-08-31T20:17:27Z

Yes, both actually. Neither seem to work.

delmyers · 2016-09-01T18:10:36Z

@NewProggie,

Can you please post your complete launch.json? The way to get this to work would normally be via the "environment" option in the launch.json.

NewProggie · 2016-09-02T06:26:26Z

@delmyers This is my launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch MyProgram",
            "type": "cppdbg",
            "request": "launch",
            "targetArchitecture": "x64",
            "cwd": "${workspaceRoot}/../../",
            "environment": [
                {
                    "name": "DYLD_FRAMEWORK_PATH",
                    "value": "/path/to/custom/lib/"
                },
                {
                    "name": "MY_ROOT",
                    "value": "${workspaceRoot}/../../"
                }
            ],
            "program": "${workspaceRoot}/../../bin/my_executable",
            "args": [],
            "stopAtEntry": false,
            "externalConsole": true,
            "linux": {
                "MIMode": "gdb"
            },
            "osx": {
                "MIMode": "lldb"
            },
            "windows": {
                "MIMode": "gdb"
            }
        }
    ]
}

And this is my tasks.json

{
    "version": "0.1.0",
    "command": "make",
    "isShellCommand": true,
    "osx": {
        "options": {
            "env": {
                "DYLD_FRAMEWORK_PATH":"/path/to/custom/lib/",
                "ARCH":"macosx",
                "COMP":"gcc"
            }
        }
    },
    "options": {
        "cwd": "${workspaceRoot}",
        "env": {
            "MY_ROOT":"${workspaceRoot}/../../",
            "STATE":"release"
        }
    },
    "tasks": [
        {
            "taskName": "my_executable",
            "suppressTaskName": true,
            "echoCommand": false,
            "isBuildCommand": true,
            "showOutput": "always",
        }
    ]
}

If I start a new bash shell without loading any environment however, I can debug my executable sucessfully:

$ env - "$(command -v bash)" --noprofile --norc 
bash-3.2$ export DYLD_FRAMEWORK_PATH=/path/to/custom/lib
bash-3.2$ export MY_ROOT=/foo/bar
bash-3.2$ lldb ./my_executable
...

Edit: This is the error message I am getting. This is the same as if I would have tried to debug my executable without exporting the previously mentioned environment variables

Launching: '/foo/bar/../../bin/my_executable'
Working directory: '/foo/bar'
1 arguments:
argv[0] = '/foo/bar/../../bin/my_executable'
dyld: Library not loaded: @rpath/My_Lib
  Referenced from: /foo/bar/../../bin/my_executable
  Reason: image not found

delmyers · 2016-09-02T17:35:04Z

@edumunoz, can you take a look at this?

edumunoz · 2016-09-07T18:29:47Z

Thanks for the bug report, @NewProggie!

I am able to repro it. We will be changing the way environment variables are set.

NewProggie · 2016-09-07T18:34:31Z

@edumunoz Nice, thanks. Will you keep us updated here? Can we expect an update any time soon?

NewProggie · 2016-09-13T10:32:12Z

@edumunoz Was your fix included in the recently released version 0.9.1 (https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools)?

edumunoz · 2016-09-13T16:37:19Z

No, sorry. I will comment on this issue once the fix is released.

pieandcakes · 2016-09-23T17:06:01Z

@NewProggie This should be in our latest release 0.9.2. If you download the extension and find that it is still an issue, please reopen this Issue with us.

NewProggie · 2016-09-26T07:46:51Z

Debugging works fine now. Thanks a lot!

YLiu-5 · 2020-07-06T04:40:52Z

Hi, I have the same issue with the LLDB here. It is not working on my machine yet.

Version: 1.46.1
Date: 2020-06-17T21:17:14.222Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 18.6.0

Below is my launch.json file,

`{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [

    {
        "name": "(lldb) Launch",
        "type": "cppdbg",
        "request": "launch",
        "program": "${workspaceFolder}/hFEM_OOP",
        "environment": [
            {
                "name": "DYLD_LIBRARY_PATH",
                "value": "/path/to/lib"
            }
        ],
        "args": [],
        "stopAtEntry": false,
        "cwd": "${workspaceFolder}",
        "externalConsole": false,
        "MIMode": "lldb",
    }
]

}`

Then I got the following error,
@"dyld: Library not loaded: src/libhpro.dylib\r\n" @" Referenced from: /Applications/deal.II.app/Contents/Resources/examples/hfem/build/hFEM_OOP\r\n" @" Reason: image not found\r\n"

In the terminal I have no issue setting the environment variable.

pieandcakes · 2020-07-06T18:26:20Z

FYI: @WardenGnaw for macOS environment variable issues. It looks like the customer is trying to set debugger environment variables.

@YLiu-5 Environment variables are set for the Debuggee and not the debugger.

YLiu-5 · 2020-07-07T00:13:02Z

FYI: @WardenGnaw for macOS environment variable issues. It looks like the customer is trying to set debugger environment variables.

@YLiu-5 Environment variables are set for the Debuggee and not the debugger.

In the terminal I would type

$ lldb ./my_executable (lldb) env DYLD_LIBRARY_PATH=/my/foo/bar (lldb) run

Can you suggest what should I do in vscode to set the environment variable for the LLDB debugger?

pieandcakes · 2020-07-07T23:28:17Z

@YLiu-5 if you have the lldb command, you can try setupCommands to add direct commands to lldb before we start debuggee execution.

YLiu-5 · 2020-07-08T04:15:09Z

@pieandcakes I tried but to no avail. The setupCommands will not load the environment variable for me.

Below is my launch.json file.

`
{
"version": "0.2.0",
"configurations": [

    {
        "name": "(lldb) Launch",
        "type": "cppdbg",
        "request": "launch",
        "program": "${workspaceFolder}/hFEM_OOP",
        "environment": [
            {
                "name": "DYLD_LIBRARY_PATH",
                "value": "/usr/local/hlibpro-2.8.1/lib"
            }
        ],
        "args": [],
        "stopAtEntry": false,
        "cwd": "${workspaceFolder}",
        "externalConsole": false,
        "MIMode": "lldb",
        "setupCommands": [
            { "text": "env DYLD_LIBRARY_PATH=/usr/local/hlibpro-2.8.1/lib", 
              "description": "load environment variable", 
              "ignoreFailures": true },
        ],
    }
]

}
`

The output in debug console,
@"dyld: Library not loaded: src/libhpro.dylib\r\n" @" Referenced from: /Applications/deal.II.app/Contents/Resources/examples/hfem/build/hFEM_OOP\r\n" @" Reason: image not found\r\n"

The debug process is paused on exception.

pieandcakes · 2020-07-10T19:54:20Z

Can you include engine logging so we can see what the response from that command is? I don't have enough information to go off of but if that command works in LLDB then it should work in this instance too.

YLiu-5 · 2020-07-15T09:26:48Z

Hi, I just made it work by adding the environment in the file setting.json, instead of launch.json.

fventer · 2021-09-16T17:32:20Z

This issue has not been solved yet. Environment variables not set using codelldb on MacOS using launch.json

jdgp-hub · 2021-09-16T19:55:12Z

I have no idea what you are talking about.

…

On 09/16/2021 12:32 PM fventer ***@***.***> wrote: This issue has not been solved yet. Environment variables not set using codelldb on MacOS using launch.json — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub #191 (comment) , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKNPPZCHHYRIIOSROQ5FHMTUCIS3BANCNFSM4COH6J7Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

gintsgints · 2023-06-20T07:51:54Z

Imho in this case environment is set uncorrectly. It should be done this way:

 "version": "0.2.0",
  "configurations": [
    {
      "type": "lldb",
      "request": "launch",
      "name": "Debug executable 'balcia-bdt-v2'",
      "env": {
        "RUST_BACKTRACE": "1"
      },

harry-nutsfi · 2024-10-18T10:56:13Z

Imho in this case environment is set uncorrectly. It should be done this way:

"version": "0.2.0",
"configurations": [
{
"type": "lldb",
"request": "launch",
"name": "Debug executable 'balcia-bdt-v2'",
"env": {
"RUST_BACKTRACE": "1"
},

yes, this is the correct way.

sridmad added the debugger label Aug 31, 2016

delmyers assigned edumunoz Sep 2, 2016

edumunoz changed the title ~~Debugger doesn't respect setupCommands settings~~ Environment variables don't work with LLDB Sep 12, 2016

pieandcakes closed this as completed Sep 23, 2016

xoob mentioned this issue May 2, 2017

Environment variables undefined during debug. microsoft/vscode-go#947

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Environment variables don't work with LLDB #191

Environment variables don't work with LLDB #191

NewProggie commented Aug 31, 2016 •

edited

Loading

paulmaybee commented Aug 31, 2016

NewProggie commented Aug 31, 2016

delmyers commented Sep 1, 2016

NewProggie commented Sep 2, 2016 •

edited

Loading

delmyers commented Sep 2, 2016

edumunoz commented Sep 7, 2016

NewProggie commented Sep 7, 2016

NewProggie commented Sep 13, 2016

edumunoz commented Sep 13, 2016 •

edited

Loading

pieandcakes commented Sep 23, 2016

NewProggie commented Sep 26, 2016

YLiu-5 commented Jul 6, 2020

pieandcakes commented Jul 6, 2020 •

edited

Loading

YLiu-5 commented Jul 7, 2020

pieandcakes commented Jul 7, 2020

YLiu-5 commented Jul 8, 2020

pieandcakes commented Jul 10, 2020

YLiu-5 commented Jul 15, 2020

fventer commented Sep 16, 2021

jdgp-hub commented Sep 16, 2021 via email

gintsgints commented Jun 20, 2023

harry-nutsfi commented Oct 18, 2024

Environment variables don't work with LLDB #191

Environment variables don't work with LLDB #191

Comments

NewProggie commented Aug 31, 2016 • edited Loading

paulmaybee commented Aug 31, 2016

NewProggie commented Aug 31, 2016

delmyers commented Sep 1, 2016

NewProggie commented Sep 2, 2016 • edited Loading

delmyers commented Sep 2, 2016

edumunoz commented Sep 7, 2016

NewProggie commented Sep 7, 2016

NewProggie commented Sep 13, 2016

edumunoz commented Sep 13, 2016 • edited Loading

pieandcakes commented Sep 23, 2016

NewProggie commented Sep 26, 2016

YLiu-5 commented Jul 6, 2020

pieandcakes commented Jul 6, 2020 • edited Loading

YLiu-5 commented Jul 7, 2020

pieandcakes commented Jul 7, 2020

YLiu-5 commented Jul 8, 2020

pieandcakes commented Jul 10, 2020

YLiu-5 commented Jul 15, 2020

fventer commented Sep 16, 2021

jdgp-hub commented Sep 16, 2021 via email

gintsgints commented Jun 20, 2023

harry-nutsfi commented Oct 18, 2024

NewProggie commented Aug 31, 2016 •

edited

Loading

NewProggie commented Sep 2, 2016 •

edited

Loading

edumunoz commented Sep 13, 2016 •

edited

Loading

pieandcakes commented Jul 6, 2020 •

edited

Loading