Difference between revisions of "SCOOP-A4: Debugger adaptation"

(New page: {{UnderConstruction}} Category:Concurrency_(SCOOP) Team: Jocelyn, Ian First thoughts about debugger/thread/SCOOP * Need to be able to switch threads ** Actually this is already possi...)
 
 
Line 5: Line 5:
 
First thoughts about debugger/thread/SCOOP
 
First thoughts about debugger/thread/SCOOP
  
* Need to be able to switch threads
+
# Need to be able to switch threads
** Actually this is already possible, but for SCOOP, we'll need to identify the technical thread (for scheduler..) from the application thread
+
#* Actually this is already possible, but for SCOOP, we'll need to identify the technical thread (for scheduler..) from the application thread
 
+
# Need to be able to debug after deadlock
* Need to be able to debug after deadlock
+
#* this requires an extra thread (Manu)
** this requires an extra thread (Manu)
+
# Need to pause & resume threads
 
+
# Need to be able to step staying on the same thread.
* Need to pause & resume threads
+
#* This might be easy to achieve soon, for current EiffelStudio's need (and thus for SCOOP as well)
 
+
* Need to be able to step staying on the same thread.
+
** This might be easy to achieve soon, for current EiffelStudio's need (and thus for SCOOP as well)
+

Latest revision as of 00:30, 25 May 2010

Construction.png Not Ready for Review: This Page is Under Development!

Team: Jocelyn, Ian

First thoughts about debugger/thread/SCOOP

  1. Need to be able to switch threads
    • Actually this is already possible, but for SCOOP, we'll need to identify the technical thread (for scheduler..) from the application thread
  2. Need to be able to debug after deadlock
    • this requires an extra thread (Manu)
  3. Need to pause & resume threads
  4. Need to be able to step staying on the same thread.
    • This might be easy to achieve soon, for current EiffelStudio's need (and thus for SCOOP as well)