Feature Requests item #773763, was opened at 2003-07-18 11:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=438938&aid=773763&group_id=44253
Category: Debugger
Group: Medium (< 1 pair-month)
Status: Open
Priority: 5
Submitted By: James Hsia (jhsia)
Assigned to: Nobody/Anonymous (nobody)
Summary: Refactor debugger
Initial Comment:
It is very difficult to determine which events
(currThreadSsuspended, currThreadSet,
threadLocationUpdated, etc.) are fired by which actions
(breakpoint reached, changing the current thread,
stepping, etc.) in the debugger. This makes it hard to
change the behavior of events or of specific actions.
It would be ideal if there were a clearer chain of
methods called and events fired by each action.
Also, the current thread in the debugger needs to
always be in sync with the current debug interpreter.
Right now, during stepping and resuming, the debug
interpreter is removed and the next debug interpreter
in line (or the default interpreter if there are no
other debug interpreters) is added, but the current
thread is not changed. We would like stepping to not
touch the current thread or the current debug
interpreter, while resuming should remove both.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=438938&aid=773763&group_id=44253
|
