And here is another bug (which is in the control flow of a regular
exception):

Process >> debug: context title: title full: bool
	"Open debugger on self with context shown on top"

	| topCtxt |
	topCtxt := self isActiveProcess ifTrue: [thisContext] ifFalse: [self
suspendedContext].
	(topCtxt hasContext: context) ifFalse: [^ self error: 'context not in
process'].
	ToolSet debug: self context: context label: title contents: nil fullView:
bool.

Because we cheat with #activeProcess and #effectiveProcess, #isActiveProcess
will always be true and thus use thisContext, which would be wrong...?
Hmpf... Stepping over code that raises exceptions seems to be quite brittle
just now...

Process >> isActiveProcess
	^ self == Processor activeProcess

ProcessorScheduler >> activeProcess
	^activeProcess effectiveProcess

Process >> step
	^Processor activeProcess
		evaluate: [suspendedContext := suspendedContext step]
		onBehalfOf: self

Best,
Marcel



--
View this message in context: http://forum.world.st/Is-this-a-bug-with-Step-Over-tp4830736p4833880.html
Sent from the Squeak - Dev mailing list archive at Nabble.com.