Closed 0BananaBig0 closed 2 years ago
"breakpointers": {
Typo
@puremourning Eventhoug I change "breakpointers" to "breakpoints" , this problem still occurs.
just carefully read the documentation that explains how to configure exception breakpoints. You have it wrong in your config (in the wrong place), this is not a bug.
Vimspector Debug Info
--------------------------------------------------------------------------------
ConnectionType: job
Adapter:
--------------------------------------------------------------------------------
{
"attach": {
"pidProperty": "processId",
"pidSelect": "ask"
},
"command": [
"/home/lwx/.vim/plugged/vimspector/gadgets/linux/vscode-cpptools/debugAdapters/bin/OpenDebugAD7"
],
"configuration": {
"args": [],
"cwd": "/data/lwx/W",
"environment": [],
"type": "cppdbg"
},
"name": "cppdbg",
"env": {},
"cwd": "/data/lwx/W/src/W/E/A/L"
}
--------------------------------------------------------------------------------
Configuration:
--------------------------------------------------------------------------------
{
"adapter": "vscode-cpptools",
"variables": {},
"configuration": {
"name": "cpp:launch",
"stopAtEntry": true,
"type": "cppdbg",
"request": "launch",
"program": "/data/lwx/W/bin/W",
"args": [
"-script",
"/data/lwx/W/Y/P/T/a/scr/A"
],
"cwd": "/data/l/W/Y/P/T/a/run",
"environment": [],
"externalConsole": true,
"MIMode": "gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
]
},
"breakpoints": {
"exception": {
"cpp_throw": "Y",
"cpp_catch": "Y"
}
}
}
--------------------------------------------------------------------------------
API Prefix:
Launch/Init: True / True
Workspace Root: /data/lwx/W
Launch Config:
--------------------------------------------------------------------------------
{
"args": [
"-script",
"/data/lwx/W/Y/P/T/a/scr/A"
],
"cwd": "/data/lwx/W/Y/P/T/a/run",
"environment": [],
"type": "cppdbg",
"name": "cpp:launch",
"stopAtEntry": true,
"request": "launch",
"program": "/data/lwx/W/bin/W",
"externalConsole": true,
"MIMode": "gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
]
}
--------------------------------------------------------------------------------
Server Capabilities:
--------------------------------------------------------------------------------
{
"supportsConfigurationDoneRequest": true,
"supportsFunctionBreakpoints": true,
"supportsConditionalBreakpoints": true,
"supportsEvaluateForHovers": true,
"exceptionBreakpointFilters": [
{
"filter": "all",
"label": "All C++ Exceptions",
"default": false,
"supportsCondition": true,
"conditionDescription": "std::out_of_range,std::invalid_argument"
}
],
"supportsSetVariable": true,
"supportsGotoTargetsRequest": true,
"supportsCompletionsRequest": true,
"completionTriggerCharacters": [],
"supportsModulesRequest": true,
"supportedChecksumAlgorithms": [],
"supportsValueFormattingOptions": true,
"supportsLogPoints": true,
"supportsSetExpression": true,
"supportsDataBreakpoints": true,
"supportsReadMemoryRequest": true,
"supportsDisassembleRequest": true,
"supportsClipboardContext": true,
"supportsSteppingGranularity": true,
"supportsInstructionBreakpoints": true,
"supportsExceptionFilterOptions": true
}
--------------------------------------------------------------------------------
Line Breakpoints:
--------------------------------------------------------------------------------
{
"/data/lwx/W/src/W/main.cpp": []
}
--------------------------------------------------------------------------------
Func Breakpoints:
--------------------------------------------------------------------------------
[]
--------------------------------------------------------------------------------
Ex Breakpoints:
--------------------------------------------------------------------------------
{
"filters": []
}
--------------------------------------------------------------------------------
It still happens @puremourning
Your exception specification is:
"breakpoints": {
"exception": {
"cpp_throw": "Y",
"cpp_catch": "Y"
}
}
the message you are receiving:
all: Break on All C++ Exceptions (Y/N/default: N)? N
Per the documentation:
Your message has all
at the beginning, so you need to use all
as the key for the exception breakpoint configuration, e.g.:
"breakpoints": {
"exception": {
"all": "N",
}
}
You now have all the required information copy/pasted by me, written and documented by me, and tested, by me. I hope you enjoy it.
Description
After update vscode-cpptools from 1.9.7 to 1.9.8, evertime I start the vimspector to debug my cpp codes or clear all breakpoints, it will ask me "all: Break on All C++ Exceptions (Y/N/default: N)? N". Although I changed my .vimspector.json file, this still happen.
Works in vim?
Reproducable in Vim
Works with clean config?
No
Sample project works?
No sample project for this filetype
Minimal Reproduction
List of steps to reproduce:
1, open vim 2, begin to debug
Expected Behaviour
Do not ask me "all: Break on All C++ Exceptions (Y/N/default: N)? N"
Actual Behaviour
Ask me "all: Break on All C++ Exceptions (Y/N/default: N)? N"
Additional information
vscode-cpptools1.9.7 has no this problem.
Installation Type
Plugin Manager (git clone)
Vimspector version
4e68dc10ba00a4990090872dce2b15127e28fe55
Debug Info
Log file
Vim version
Python version
No response
Neovim diagnostics
No response
Operating System
Linux dggpcotgpu00004 3.10.0-1127.10.1.el7.x86_64 #1 SMP Wed Jun 3 14:28:03 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Declaration