Pharo Issue Tracker - FogBugz (Case [Issue]12193) Debugging - temp variable mapping wrong in the debugger

FogBugz Notification

	Marcus Denker resolved Case 12193: temp variable mapping wrong in the debugger and assigned it to Marcus Denker: Bug in Debugging: 2. External • You are subscribed to this case

I have done the following:

1) added #willCreateBlock that checks if the next bytecode is a block creation bc
2) #stepToSendOrReturn now checks for blocks, too.

In the old bytecode, block creation was done with a message send, so #stepToSendOrReturn never run across a block creation boundary. Now, with the block creation bytecode, if you step, it will run until the first send of access in the block, executing the block setup code, which I think is what causes the bug.

Name: SLICE-Issue-12193-temp-variable-mapping-wrong-in-the-debugger-MarcusDenker.1
Author: MarcusDenker
Time: 19 November 2013, 10:21:49.505608 am
UUID: a8d2df33-bb44-4b82-bd24-34e590047ed7
Ancestors:
Dependencies: Kernel-MarcusDenker.1684

temp variable mapping wrong in the debugger

(Issue 12193)

Status changed:
Work Needed

Resolved (Fix Review Needed)

	Priority: 2 – Really Important		Status: Resolved (Fix Review Needed)
	Assigned to: Marcus Denker		Milestone: Pharo3.0

Go to Case

No longer need updates? Unsubscribe from this case.

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

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