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

LLDB-DAP in VSC doesn't respect "disableASLR": false unless you also do settings set target.disable-aslr false #94338

Closed
HolyBlackCat opened this issue Jun 4, 2024 · 1 comment · Fixed by #129753
Labels

Comments

@HolyBlackCat
Copy link

When you try to debug in Docker using LLDB-DAP, by default it fails because it's unable to disable the ASLR.

Adding "disableASLR": false, to launch.json is supposed to fix it, but currently you need both that and "initCommands": ["settings set target.disable-aslr false"], for it to work.

Ideally the former should be enough (or if either one worked, that would be perfect). I could swear that the former was enough at some point (maybe when I was using v0.2.0 VSC extension I compiled myself, while now I'm using v0.2.1 from the marketplace).

I'm using lldb-dap-18 v18.1.3 from apt.llvm.org on Ubuntu 22.04.

@llvmbot
Copy link
Member

llvmbot commented Jun 4, 2024

@llvm/issue-subscribers-lldb

Author: Egor (HolyBlackCat)

When you try to debug in Docker using LLDB-DAP, by default it fails because it's unable to disable the ASLR.

Adding "disableASLR": false, to launch.json is supposed to fix it, but currently you need both that and "initCommands": ["settings set target.disable-aslr false"], for it to work.

Ideally the former should be enough (or if either one worked, that would be perfect). I could swear that the former was enough at some point (maybe when I was using v0.2.0 VSC extension I compiled myself, while now I'm using v0.2.1 from the marketplace).

I'm using lldb-dap-18 v18.1.3 from apt.llvm.org on Ubuntu 22.04.

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

Successfully merging a pull request may close this issue.

4 participants