Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The server log buffer, created with dap-start-debugging does not keep environment variables for reexecution using recompile #510

Open
dudinea opened this issue Sep 23, 2021 · 0 comments · May be fixed by #511

Comments

@dudinea
Copy link

dudinea commented Sep 23, 2021

The problem

The server log buffer, created with dap-start-debugging-noexpand does not keep environment variables for re-execution using recompile

How to reproduce:

run

 (dap-start-debugging-noexpand '(:program-to-start "/bin/sh  -c 'echo FOO=$FOO'" :environment-variables (("FOO" . "BAR")) :name "test-compile-bug" :cwd "." :skip-debug-session t))

The output will be like:

-*- mode: dap-server-log; default-directory: "/usr/bin/" -*-
Debug Adapter started at Thu Sep 23 09:35:56

/bin/sh  -c 'echo FOO=$FOO'
FOO=BAR

Debug Adapter finished at Thu Sep 23 09:35:56

Press g in the log buffer, now the output will be like:

-*- mode: dap-server-log; default-directory: "/usr/bin/" -*-
Debug Adapter started at Thu Sep 23 09:38:58

/bin/sh  -c 'echo FOO=$FOO'
FOO=

Debug Adapter finished at Thu Sep 23 09:38:58

What is expected

The command is re-executed using same environment

Affected use cases

I run tests dap-java-run-test-class which uses an environment variable to pass java classpath.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant