Debugging Setup Guide With Launch Configurations and Breakpoint Practice
Set up debugging for a project and practise the workflow.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Guide me in setting up debugging in VS Code. Language and framework: [LANGUAGE_AND_FRAMEWORK]. How I run the project now: [RUN_COMMAND]. Operating system: [OPERATING_SYSTEM]. A bug I want to practise on: [BUG_DESCRIPTION]. Explain what a launch configuration is, then draft one for my project with comments on each field and the extension or runtime it needs [VERIFY exact names]. Give a practice exercise: set a breakpoint, step over and into, watch variables, use conditional breakpoints and logpoints, inspect the call stack, and find the cause of the bug. Provide a debugging checklist (reproduce, narrow, form a hypothesis, test, fix, add a test) and a troubleshooting table for common issues (breakpoints not hit, wrong interpreter, source maps). Settings and extensions change; mark names, fields and commands [VERIFY] against the current documentation. Do not execute anything. Add a worked practice bug: a function returns the wrong average because it divides by the list length minus one; walk through setting a breakpoint, watching the variables and finding the line, then adding a unit test with expected output 20 for the inputs 10, 20, 30. Mark commands [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.