Breakpoints in an editor
A marker set on a line of code that pauses the program there when it runs, so you can inspect variables and step through. Set one by clicking beside the line; click again to remove it.
Understanding Breakpoints in an editor in VCE Applied Computing U1O2
What it does: Starting the debugger runs the program until it reaches a breakpoint, then pauses so you can look at the variables. Most editors let you click beside the line number to place a breakpoint, often shown as a red dot. You do not add any code. Clicking the marker again toggles the breakpoint off. The code stays unchanged. Pausing just before the suspect line lets you inspect the variables and find where things go wrong. Breakpoints do not speed up a program. A breakpoint on a comment or blank line is skipped, and a normal run ignores breakpoints, so no pause happens.
Common mistakes: breakpoint is a function, so it needs brackets to be called. Without them nothing pauses. It should be breakpoint(). Python is case sensitive, so Breakpoint() is not defined and causes a NameError. It should be breakpoint() in lowercase.
Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.
This module's key terms are also in a printable crossword (Modules 89–124) and word search (Modules 8–124).
Take this worksheet further — free with Cloodit
Each concept is reinforced from every angle — learned, then applied, then tested.
Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.
Over 100 of them, across seven natural biomes.
Turns their work into revision material ready for Flash Cards and Exam study.
Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.
Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.
Quick Questions
Match the Pairs
Key Term
breakpointFill in the Blanks
Spot the Error
Student with a class code? Join your class →