Maintain virtual MuranoPL stack trace

Registered by Stan Lagun

MuranoPL need to maintain its own stack trace that is independent on underlying Python stack trace and the fact that MuranoPL methods are executed in different green threads. Stack trace is a list of stack frames. Each stack frame has a execution pointer that allows to identify current instruction (or instruction caller). Ideally in debug mode it should be possible to access local stack frame variables as well. It should be possible to obtain current stack trace at any moment or place, pretty-print it or get caller class/object

Blueprint information

Status:
Complete
Approver:
Ruslan Kamaldinov
Priority:
High
Drafter:
Stan Lagun
Direction:
Approved
Assignee:
Stan Lagun
Definition:
Approved
Series goal:
Accepted for juno
Implementation:
Implemented
Milestone target:
milestone icon 2014.2
Started by
Stan Lagun
Completed by
Ruslan Kamaldinov

Related branches

Sprints

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.