-
Type: Debugger
**Describe the bug**
- OS and Version: **Windows_NT x64 10.0.19042**
- VS Code Version: **1.51.1 (also tried with Insiders, the issue still occurs)**
- C/C++ Extension Version: **…
-
The debuginfo tests should probably use a specific debugger, like maybe an lldb we build with the compiler, so that they work consistently. In practice, they have [been effectively broken on user's ma…
-
## Environment
* **IntelliJ Rust plugin version:** 0.4.189.5234-223
* **Rust toolchain version:** 1.68.0 (2c8cc3432 2023-03-06) x86_64-pc-windows-msvc
* **IDE name and version:** CLion 2022.3.2 (…
-
### Go version
go version go1.22.6 darwin/arm64
### Output of `go env` in your module/workspace:
```shell
GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/larry/Library/Caches/go-bu…
-
There are certain symbols that the debugger (windbg/lldb) understands but BN does not know about. For example, when a register points to the address of a Windows API function, it would be great if we …
-
The test case comes from #107144.
I have a question: in the context of C, would changing the order of elements in a union impact the memory content of the union?
In a union,
- the size of the…
-
### Environment
- OS and version: macOS Monterey 12.4
- VS Code: 1.68.0
- C/C++ extension: 1.11.0
- OS and version of remote machine (if applicable): no
- GDB / LLDB version: 13.0.1
### Bu…
-
Hi, I am trying to debug a program which takes a input file. It works in command line when I run it as ./a.out
-
```
#0 0x0000000105657228 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/opt/llvm18/bin/lldb+0x100022228)
#1 0x000000010565540a llvm::sys::RunSignalHandlers() (/opt/llvm18/bin/lldb+0x1000204…
-
### Brief Issue Summary
Cmaketools attempts to launch lldb on linux, something that is explicitely not supported by cpptools.
### CMake Tools Diagnostics
_No response_
### Debug Log
_No…