Make lldb debug work to debug with cpp and rust

[gengjiawen]

Repo: https://github.com/gengjiawen/node-debug
Gitpod: https://gitpod.io/#https://github.com/gengjiawen/node-debug

debug config:

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "lldb",
            "initCommands":["settings set target.disable-aslr false"],
            "request": "launch",
            "name": "Debug",
            "program": "node",
            "args": ["hello.js"],
            "cwd": "${workspaceFolder}"
        }
    ]
}

Current status: not working

'A' packet returned an error: 8

Working container config: "runArgs": [ "--cap-add=SYS_PTRACE", "--security-opt", "seccomp=unconfined" ], https://github.com/gengjiawen/node-debug/blob/f1aaeea4aed61a037f28397aa11d907525ce35fc/.devcontainer/devcontainer.json#L13

I think fixing vscode-lldb on gitpods will bring debug native language (c, cpp, rust) to the next level.

Related:

• Rust LLDB debugging fails #1331
• GDB isn't working #544

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[gengjiawen]

not stale

[sagor999]

@Furisto is this supported with our runtime config? and if not, is this a complex task or an easy fix?

[Furisto]

@sagor999 Hard to say honestly. It looks we already tried to enable it, but it is obviously not working. We have to look into which layer in our stack causes the problem. Then we need to check if this can be done without introducing security risk.

[sagor999]

@kylos101 added it to our inbox

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[david-bakin]

@axonasif - any chance to mark this "never stale"?

[aledbf]

@gengjiawen please try again. Check the workspace lands in us60 or eu60.

[gengjiawen]

@gengjiawen please try again. Check the workspace lands in us60 or eu60.

the breakpoint not working on my side.

[gengjiawen]

Second try works, not sure why ?

[aledbf]

the breakpoint not working on my side.

I cannot reproduce that behavior. That said, the codelldb process uses 100% of the CPU, and after ~15s the breakpoint is reached.

[gengjiawen]

I can't reproduce the bug. Thx for the great work.

[jenting]

Move the status to Done because we can't reproduce this bug.

[kasperk81]

'A' packet returned an error: 8

still getting the same error in terminal. what is needed to make lldb work in gitpod terminal?

Gitpod: https://gitpod.io/#https://github.com/gengjiawen/node-debug

ran sudo apt install lldb then lldb ls (or lldb node or any binary you wish to run under debugger) and then run in lldb's repl:

Current executable set to 'ls' (x86_64).
(lldb) run
error: process launch failed: 'A' packet returned an error: 8

otoh, gdb just works in the same terminal: gdb ls and run in its repl.