Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prevent cppvsdbg debug step over Standard Library #13189

Open
samantrader opened this issue Jan 24, 2025 · 2 comments
Open

prevent cppvsdbg debug step over Standard Library #13189

samantrader opened this issue Jan 24, 2025 · 2 comments
Labels
debugger more info needed The issue report is not actionable in its current state

Comments

@samantrader
Copy link

Hi
how can prevent cppvsdbg debug step over Standard Library and just step over my source code (rust app) in vs code

@sean-mcmanus sean-mcmanus added debugger more info needed The issue report is not actionable in its current state labels Jan 24, 2025
@sean-mcmanus
Copy link
Contributor

@samantrader What do you mean by "step over Standard Library"?

@samantrader
Copy link
Author

samantrader commented Jan 25, 2025

Hi
I want debug a rust sciter application and from first breakpoint press f10 to go ahead but after multi pressing f10 debugger go to function.rs and show error :
the editor could not be opened because the file was not found

path of file : C:\rustc\eeb90cda1969383f56a2637cbd3037bdf598841c\library\core\src\ops\function.rs

i want debugger continue just with my written source and donot enter in rust library file

my launch.json:

{
"version": "0.2.0",
"configurations": [
{
"name": "(Windows) Launch",
"type": "cppvsdbg",
"request": "launch",
"program": "${workspaceRoot}/target/debug/myexe.exe",
"args": [],

        "cwd": "${workspaceRoot}",
        "environment": [],
        "externalConsole": false,
        "sourceFileMap": {
          "C:\\Users\\admin\\.cargo\\registry\\src": "C:\\fake-path"
        }       
       
    }
    
]

}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debugger more info needed The issue report is not actionable in its current state
Projects
None yet
Development

No branches or pull requests

2 participants