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

Manuscript Notification

	Thomas Dupriez revised a previous entry on Case 22474: Debugger should step silently over #halt: Bug in Debugging: 1. Pharo Image • You are subscribed to this case

I wanted to find who was calling MorphicUIManager>>debugProcess:context:label:fullView:notification: during the stepping over the second halt of your code snippet to open the empty pre-debug window.

I tried to:

- execute your code snippet
- step over until just before reaching the second halt
- add a `self haltOnce`to the code of MorphicUIManager>>debugProcess:context:label:fullView:notification:
- step over the second halt.

This results in two identical halt windows like the one you showed. When clicking their "debug" button, both have a single stack entry: for one it is the halt method of the object containing your snippet of code, for the other it is the haltOnce method of MorphicUIManager.

So, not much luck here. :(
I don't see how to continue debugging this issue from here...

	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