Function name in BREAKPOINTS dock.

[kiv07]

Hi CodeLLDB Team,

I am currently using CodeLLDB with VScode for my debugging needs and have a question regarding the breakpoints dock. When I set breakpoints using the command "br s -n <function_name>", the breakpoints dock displays the file name and path.

launch configuration :
{
"type": "lldb",
"request": "launch",
"name": "Debug local var",
"program": "C:/Test_code/code1/a.exe",
"args": [],
"cwd": "${workspaceFolder}",
"breakpointMode": "path",
"stopOnEntry": true,
"initCommands": [
"br s -n main"
],
}

I was wondering if there is any support or a way to configure CodeLLDB to display the function name instead of the file name and path in the breakpoints dock. This feature would greatly enhance my debugging experience.

Thank you for your time and assistance. I look forward to your response.

[vadimcn]

This text is generated by VSCode, a debug adapter can't change it.

But why aren't you using function breakpoints?

[kiv07]

Yes, I am aware of setting function breakpoints this way. However, I usually set function breakpoints with the command br s -n <func_name> from the LLDB command prompt in VSCode.

So, setting breakpoints using “Add Function Breakpoint” in the UI, shows the function name.
But if we set breakpoints from the LLDB command prompt, will shows the file name and path. This behavior is not related to CodeLLDB and cannot be changed by it. Is my understanding correct? Please correct me if I’m wrong.

Thank you for your time and assistance. I look forward to your reply.

[vadimcn]

That's right: when a breakpoint is created from LLDB command line, the adapter sends a notification to VSCode. All the information it can provide is contained within the Breakpoint struct; VSCode then decides how to display it. Ask you can see, there is no field for the function name.
If you use "Add Function Breakpoint”, the flow of the information is reversed: VSCode asks the adapter to set a function breakpoint, so it knows which function the breakpoint is being set on.

[kiv07]

Thanks a lot for the clarification.