Jump to: navigation, search

Difference between revisions of "CDT/MultiCoreDebugWorkingGroup/SynchronizedOperations"

(New page: == Synchronized Run Control Operations == Some multi-core debuggers allow performing synchronized operations on multiple cores. Each run control operation will affect all chosen cores sy...)
 
Line 2: Line 2:
  
 
Some multi-core debuggers allow performing synchronized operations on multiple cores.  Each run control operation will affect all chosen cores synchronously.  Allowing the debugger or the hardware to operate on multiple cores minimizes the skid, or the time lag, in when the operations are carried out on the different cores.
 
Some multi-core debuggers allow performing synchronized operations on multiple cores.  Each run control operation will affect all chosen cores synchronously.  Allowing the debugger or the hardware to operate on multiple cores minimizes the skid, or the time lag, in when the operations are carried out on the different cores.
 +
 +
== Grouped Run Control Operations ==
 +
 +
Run Control Operations (step, resume, suspend) should be allowed on multiple debug entries on a single user operation.  The user should be able to perform such operations on one or more processes/threads/cores/groups.

Revision as of 13:14, 23 November 2010

Synchronized Run Control Operations

Some multi-core debuggers allow performing synchronized operations on multiple cores. Each run control operation will affect all chosen cores synchronously. Allowing the debugger or the hardware to operate on multiple cores minimizes the skid, or the time lag, in when the operations are carried out on the different cores.

Grouped Run Control Operations

Run Control Operations (step, resume, suspend) should be allowed on multiple debug entries on a single user operation. The user should be able to perform such operations on one or more processes/threads/cores/groups.