Pharo Issue Tracker - Manuscript (Case [Issue]22474) Debugging - Debugger should step silently over #halt

Manuscript Notification

	Ben Coman opened Case 22474: Debugger should step silently over #halt and assigned it to Everyone: Bug in Debugging: 1. Pharo Image • You are subscribed to this case

I'll often put several breakpoints in code like this...
```
debug := true.
"Somewhere else in application code..."
debug ifTrue: [ self halt ].
1 + 1. "Representing some longer bit of application code"
debug ifTrue: [ self halt ].
2 + 2. "Representing some longer bit of application code"
debug ifTrue: [ self halt ].
3 + 3. "Representing some longer bit of application code"
```
While stepping through code after hitting the first halt,
I am used to subsequent halts being silently stepped over.
I just confirmed this with http://files.pharo.org/platform/Pharo6.0-win.zip
and also build 60541 started from PharoLauncher.

However build 71231 and build 60542 do not silently step over a #halt.
Each produces slightly different results (pics attached).

	Priority: 2 – Really Important		Status: Work Needed
	Assigned to: Everyone		Milestone: Pharo7.0

Go to Case

No longer need updates? Unsubscribe from this case.

Don't want Manuscript notifications anymore? Update your preferences.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker