Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "DSDP/DD/MultiContext"
m |
m (→Use cases) |
||
| Line 11: | Line 11: | ||
| − | * I. Programs with multiple threads | + | * '''I. Programs with multiple threads''' |
| − | + | ||
*;1 Two or more threads interacting : User is debugging a program with multiple threads which are interacting with each other. | *;1 Two or more threads interacting : User is debugging a program with multiple threads which are interacting with each other. | ||
*:; a) Debugging threads which contend for the same lock. : | *:; a) Debugging threads which contend for the same lock. : | ||
| Line 27: | Line 26: | ||
*:;:# User sets another breakpoint further down in routines that access the shared data. | *:;:# User sets another breakpoint further down in routines that access the shared data. | ||
*:;:# User continues some or all of the threads which stopped at the first breakpoint so that they may reach the second breakpoint. | *:;:# User continues some or all of the threads which stopped at the first breakpoint so that they may reach the second breakpoint. | ||
| − | |||
*;2 Debugging a subset of threads : User is debugging a program with multiple threads, but he is interested only in interacting with some of the threads. | *;2 Debugging a subset of threads : User is debugging a program with multiple threads, but he is interested only in interacting with some of the threads. | ||
*:; a) User debugs with breakpoints restricted to a sub-set of threads. | *:; a) User debugs with breakpoints restricted to a sub-set of threads. | ||
| Line 37: | Line 35: | ||
*:;:# User debugs a subset of threads (using filtered breakpoints, etc.). | *:;:# User debugs a subset of threads (using filtered breakpoints, etc.). | ||
*:;:# User terminates and relaunches a process, and continues to debug the same set of threads. | *:;:# User terminates and relaunches a process, and continues to debug the same set of threads. | ||
| − | + | *:; d) Tasks submitted to a thread pool : User is debugging a routine which may be executed by any thread in a thread pool at any time, and by some threads in the thread pool at the same time. | |
*;3 Program with large number (100+) of threads : User is debugging programs with large numbers of threads and he needs to manage those threads effectively. | *;3 Program with large number (100+) of threads : User is debugging programs with large numbers of threads and he needs to manage those threads effectively. | ||
*:; a) User needs to switch between suspended threads | *:; a) User needs to switch between suspended threads | ||
| Line 44: | Line 42: | ||
*:;:# User switches focus between suspended threads to control them and examine their data. | *:;:# User switches focus between suspended threads to control them and examine their data. | ||
*:; b) Threads created/destroyed rapidly: User is debugging a process with threads being created and destroyed at a rapid rate (more than 1 thread/sec.) | *:; b) Threads created/destroyed rapidly: User is debugging a process with threads being created and destroyed at a rapid rate (more than 1 thread/sec.) | ||
| − | + | * '''II. Multiple processes that interact with each other''' | |
| − | * II. Multiple processes that interact with each other | + | *; 1 Launching multiple processes at the same time : When starting a debug session, user creates multiple processes and debugs them. |
| − | + | *; 2 Attaching to multiple processes : Instead of launching, user attaches to multiple processes and debugs them simultaneously. | |
| − | * III. Systems with multiple cores | + | *; 3 Debugging a process that forks : User is debugging a process that forks. After the fork user debugs both processes. |
| − | + | * '''III. Systems with multiple cores (On Chip Debugging)''' | |
| + | *;1 Hardware bring-up debugging : User attaches a debugger to a multi-core system for purpose of hardware configuration, such as configuring registers, IO devices, etc. (no OS, no symbol data, no executable image) | ||
| + | *;2 No-OS debugging : User attaches to a multi-core system and downloads simple executable image to each core and debugs them. | ||
| + | *;3 Debugging with OS-awareness : User attaches to a multi-core system, downloads an OS image to each, starts debugging the entire OS on each board, or specific tasks/processes running on specific cores. | ||
== Problems with workflow == | == Problems with workflow == | ||
Revision as of 18:32, 3 April 2008
This sub-group is focused on improving the workflow of multi-context debugging. Multi-context refers to simultaneous debugging of multiple cores, processes, threads, or other objects which are represented in standard debugger views. This sub-group was created following a discussion about platform debug dev: "ideas for improving multi-context debugging". The first document produced by this group was Unlink View Context proposal, this document is now deprecated and the current effort is organized around this wiki page being created by the community interested in this problem.
Use cases
Use cases to be considered when evaluating the multi-context debugging workflow.
Format:
- Family of use cases
- Use case
- Description of the use case
- Scenario
- Step
- I. Programs with multiple threads
- 1 Two or more threads interacting
- User is debugging a program with multiple threads which are interacting with each other.
- a) Debugging threads which contend for the same lock.
- When a thread blocks while stepping,
- User switches focus to another thread and steps until the lock is released,
- User switches focus back to the first thread and continues debugging.
- b) Debugging race conditions where multiple threads are reading and writing some shared data
- User sets a breakpoint at a location where a shared variable is written.
- Multiple threads hit the breakpoint
- User looks at each threads to see the thread-private data in each thread.
- User steps the threads individually to watch what happens to the shared data.
- Alternatively, user steps all threads.
- Multiple threads may hit the breakpoint at the same time.
- User sets another breakpoint further down in routines that access the shared data.
- User continues some or all of the threads which stopped at the first breakpoint so that they may reach the second breakpoint.
- 2 Debugging a subset of threads
- User is debugging a program with multiple threads, but he is interested only in interacting with some of the threads.
- a) User debugs with breakpoints restricted to a sub-set of threads.
- User creates a breakpoint on the routine to be debugged.
- User defines which threads should be allowed to hit the breakpoint.
- The threads hit the breakpoint and user steps through them.
- b) Run control for a subset of threads
- User repeatedly suspends and resumes a subset of threads.
- c) Terminating/re-launching
- User debugs a subset of threads (using filtered breakpoints, etc.).
- User terminates and relaunches a process, and continues to debug the same set of threads.
- d) Tasks submitted to a thread pool
- User is debugging a routine which may be executed by any thread in a thread pool at any time, and by some threads in the thread pool at the same time.
- 3 Program with large number (100+) of threads
- User is debugging programs with large numbers of threads and he needs to manage those threads effectively.
- a) User needs to switch between suspended threads
- User sets a breakpoint that some threads may hit.
- Some threads hit the breakpoint.
- User switches focus between suspended threads to control them and examine their data.
- b) Threads created/destroyed rapidly
- User is debugging a process with threads being created and destroyed at a rapid rate (more than 1 thread/sec.)
- II. Multiple processes that interact with each other
- 1 Launching multiple processes at the same time
- When starting a debug session, user creates multiple processes and debugs them.
- 2 Attaching to multiple processes
- Instead of launching, user attaches to multiple processes and debugs them simultaneously.
- 3 Debugging a process that forks
- User is debugging a process that forks. After the fork user debugs both processes.
- III. Systems with multiple cores (On Chip Debugging)
- 1 Hardware bring-up debugging
- User attaches a debugger to a multi-core system for purpose of hardware configuration, such as configuring registers, IO devices, etc. (no OS, no symbol data, no executable image)
- 2 No-OS debugging
- User attaches to a multi-core system and downloads simple executable image to each core and debugs them.
- 3 Debugging with OS-awareness
- User attaches to a multi-core system, downloads an OS image to each, starts debugging the entire OS on each board, or specific tasks/processes running on specific cores.
Problems with workflow
Issues with the user experience when executing the above use cases.
Proposed changes
Proposals for new features and changes in existing workflow.