Describe the bug
I am unable to use the Memory View extension to inspect memory during a debugging session. When attempting to add a memory view, I receive a "No session with the session id..." error. Despite successfully generating PDB files and being able to debug my assembly code, the extension fails to track the active debugging session.
To Reproduce
Steps to reproduce the behavior:
Compile a 32-bit assembly project using NASM and linked with lld-link (LLVM).
Generate PDB debug symbols for the output executable.
Start a debugging session in VS Code using the cppvsdbg debugger.
Once the breakpoint is hit, attempt to add a new memory view.
See issue: Error notification pops up: "No session with the session id [UUID]. Probably a bug or a debugger type that we are not tracking (check memory-view.trackDebuggers setting).. Cannot add a memory view".
Expected behavior
The Memory View should be able to attach to the cppvsdbg session and display the memory at the specified address, regardless of the fact that the binary was built with NASM and lld-link.
Screenshots
No session with the session id b28c4137-2b57-4316-a55b-06ae35bec8ff. Probably a bug or a debugger type that we are not tracking (check memory-view.trackDebuggers setting).. Cannot add a memory view
Environment:
OS: Windows 11 64bit
Version of Memory View: 0.0.29
Debugger Type: cppvsdbg
Debugger Version: 1.30.5
Additional context
I am working on a 32-bit assembly project. Even though I have correctly configured the project to generate PDB files, which allows the cppvsdbg debugger to step through the assembly code, the Memory View extension does not recognize the debugging session. I have checked the memory-view.trackDebuggers settings but the issue persists.
Describe the bug
I am unable to use the Memory View extension to inspect memory during a debugging session. When attempting to add a memory view, I receive a "No session with the session id..." error. Despite successfully generating PDB files and being able to debug my assembly code, the extension fails to track the active debugging session.
To Reproduce
Steps to reproduce the behavior:
Compile a 32-bit assembly project using NASM and linked with lld-link (LLVM).
Generate PDB debug symbols for the output executable.
Start a debugging session in VS Code using the cppvsdbg debugger.
Once the breakpoint is hit, attempt to add a new memory view.
See issue: Error notification pops up: "No session with the session id [UUID]. Probably a bug or a debugger type that we are not tracking (check memory-view.trackDebuggers setting).. Cannot add a memory view".
Expected behavior
The Memory View should be able to attach to the cppvsdbg session and display the memory at the specified address, regardless of the fact that the binary was built with NASM and lld-link.
Screenshots
No session with the session id b28c4137-2b57-4316-a55b-06ae35bec8ff. Probably a bug or a debugger type that we are not tracking (check memory-view.trackDebuggers setting).. Cannot add a memory view
Environment:
OS: Windows 11 64bit
Version of Memory View: 0.0.29
Debugger Type: cppvsdbg
Debugger Version: 1.30.5
Additional context
I am working on a 32-bit assembly project. Even though I have correctly configured the project to generate PDB files, which allows the cppvsdbg debugger to step through the assembly code, the Memory View extension does not recognize the debugging session. I have checked the memory-view.trackDebuggers settings but the issue persists.