Closed NinnOgTonic closed 3 years ago
Unfortunately it's a choice between this and crashes. I've rolled back LLDB to v12 to avoid the latter. Would be best to report this sort of stuff to upstream LLDB directly...
dear @vadimcn, you mean that this issue cannot be fixed before fixing in LLDB? I'm also suffering from this issue too 😂
@Snowapril : Don't think so. You can install the previous version, but it's gonna crash sometimes.
@vadimcn could you perhaps help me assist in how we could make a good report to the llvm project to help solve these issues?
Im not sure that the verbose log above would be sufficient for the underlying project to debug these issues?
Would we need to execute the lldb binary in a specific way for them to allow for tracing?
I would love to assist in any way possible!
@NinnOgTonic: LLDB devs wouldn't be familiar with Codelldb or its logs. They'd want a repro using plain CLI lldb.
Looks like the library breakpoint issue had already been fixed in lldb-13, so probably not worth reporting. The crash would be, but it needs a solid repro for them to be able to do anything about it.
I've installed v1.6.7, my tunnel-bin
crate depends on tunnel-lib
crate specified in cargo.toml. Now all of the breakpoints have been broken in tunnel-lib
crate. Everytime I restarted vscode, extension will update itself to latest version automatically(v1.6.7).
A debugger extension has lost Its most important debugging feature 😭.
So I'm using this debugger daily, on Linux, and I've never experienced problems with hitting breakpoints, as long as the source map is set up correctly.
Something isn't right here... Have you tried diagnosing this issue as described here?
@vadimcn I have tried, none of them works. And here are my logs
and there are my breakpoint configuration.
And without any additional settings, just downgrade to v1.6.6, all breakpoints works
I've rebuilt codelldb using the newly released LLDB 13.0.0: https://github.com/vadimcn/vscode-lldb/releases/download/v1.6.8-dev.2110040647/codelldb-bootstrap.vsix Does this fix breakpoints problems?
I've rebuilt codelldb using the newly released LLDB 13.0.0: https://github.com/vadimcn/vscode-lldb/releases/download/v1.6.8-dev.2110040647/codelldb-bootstrap.vsix Does this fix breakpoints problems?
Yes! It works! v1.6.8-dev.2110040647
I've rebuilt codelldb using the newly released LLDB 13.0.0: https://github.com/vadimcn/vscode-lldb/releases/download/v1.6.8-dev.2110040647/codelldb-bootstrap.vsix Does this fix breakpoints problems?
Yes! It works! v1.6.8-dev.2110040647
I try the v1.6.8-dev but still not work.
tasks.json
{
"version": "2.0.0",
"tasks": [
{
"label": "Build with Clang",
"type": "shell",
"command": "clang++",
"args": [
"-std=c++17",
"-stdlib=libc++",
"${file}",
"-o",
"${fileDirname}/${fileBasenameNoExtension}",
"--debug"
],
"group": {
"kind": "build",
"isDefault": true
}
}
]
}
lanuch.json
{
"version": "0.2.0",
"configurations": [
{
"type": "lldb",
"request": "launch",
"name": "Debug",
"program": "${fileDirname}/${fileBasenameNoExtension}",
"args": [],
"cwd": "${workspaceFolder}",
"preLaunchTask": "Build with Clang"
}
]
}
configuration: {
type: 'lldb',
request: 'launch',
name: 'Debug',
program: '${fileDirname}/${fileBasenameNoExtension}',
args: [],
cwd: '${workspaceFolder}',
preLaunchTask: 'Build with Clang',
__configurationTarget: 5,
noDebug: true,
relativePathBase: '/Users/do/farm/person/termial'
}
Listening on port 57390
[2021-10-04T15:32:03.800Z ERROR codelldb::debug_session] Internal debugger error: Not supported in noDebug mode.
[2021-10-04T15:32:04.390Z ERROR codelldb::debug_session] process exited with status -1 (debugserver died with signal SIGSEGV)
Debug adapter exit code=0, signal=null.
noDebug: true,
@odex21 It would seem you are launching in run mode?
Thanks, I removed the debugserver by referring here https://github.com/vadimcn/vscode-lldb/discussions/456#discussioncomment-874122, and now both the c++ and rust demos are OK.
I've rebuilt codelldb using the newly released LLDB 13.0.0: https://github.com/vadimcn/vscode-lldb/releases/download/v1.6.8-dev.2110040647/codelldb-bootstrap.vsix Does this fix breakpoints problems?
This fixes it, thanks! In my case breakpoints weren't hitting inside a shared library despite not having source map issues, removing the store version and installing from this vsix fixed the issue.
Fixed in 1.6.8
@vadimcn I'm hitting this issue using 1.6.10 — the latest release. Using Rust 1.57. I have not checked the intermediate Rust releases, but it works with Rust 1.51. I can check if you'd like; I presume it has something to do with an LLVM upgrade.
@jhpratt I you are using nightly, tracked in https://github.com/vadimcn/vscode-lldb/issues/633
OS: Ubuntu 20.04.1 LTS VSCode version: Version: 1.57.1 Extension version: 1.6.7 Compiler: rustc 1.49.0 (e1884a8e3 2020-12-29) (NB: Also tested when using latest rustc 1.54.0 (a178d0322 2021-07-26)) Build target: 1.49-x86_64-unknown-linux-gnu Debuggee: Integration test
When trying to reproduce https://github.com/vadimcn/vscode-lldb/issues/499. I encounter that no breakpoints are now ever hit. Instead the process just executes the entire target without stopping in the library source code. It appears that breakpoints inside of the integration test are triggered properly.
Rolling back to 1.6.5 or 1.6.6 reproduced the reference issue, and is able to trigger breakpoints other places in the library code.
Verbose log