Debuggers
From HP-SEE Wiki
(→Sun (Oracle Solaris) Studio) |
|||
| (8 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| + | == Eclipse CDT == | ||
| + | |||
| + | '' Section contributed by IICT-BAS '' | ||
| + | |||
| + | Eclipse CDT (C/C++ Development Tools) is a Eclipse-based C and C++ IDE. It has a large variety of features including: | ||
| + | * Managed build for various toolchains | ||
| + | * Source navigation | ||
| + | * Source knowledge tools | ||
| + | * Refactoring tools | ||
| + | * Code generation tools | ||
| + | * A variety of debugging tools such as memory, registers and disassembly viewers. | ||
| + | |||
| + | To debug applications using the CDT debugger, you need to build your application in debug mode (using the '''-g''' option). To help users familiarized with the Eclipse Debug View, CDT extends it with features for debugging C and C++ code. Using the Debug View, you can manage execution and debugging of programs in the Workbench. Management of breakpoints and variable/registers tracing is all done through the Debug View. The CDT debugger supports debugging for serial and threaded, along with debugging of multiple processes simultaneously, making it a very good tool for many purposes. | ||
| + | |||
| + | The CDT Debug MI plug-in provides support for Machine Interface-compatible debuggers, thus providing the much more reliable MI instead of the more traditional CLI. | ||
| + | |||
| + | == Jumpshot == | ||
| + | |||
| + | '' Section contributed by IICT-BAS '' | ||
| + | |||
| + | SLOG-2 is Argonne Lab's MPI logging package that includes a visualization tool, Jumpshot-4, that allows you to 'see' MPI events in your program and how they relate to time and events in other processes. Jumpshot works by reading a log file that was generated on a run of your MPI program after it has been properly instrumented. Jumpshot-4 allows seamless scrolling from the beginning to the end of the logfile at any zoom level. The main visual component in the SLOG-2 visualization program, Jumpshot-4, is the timeline canvas, which is zoomable and scrollable in both the horizontal and vertical axes. The timeline canvas can be thought of as a timeline vs. time coordinate system. Each point on the canvas is identified by two numbers: a timestamp and a timeline ID. The graphical objects contained in the SLOG-2 file are drawn on the canvas. | ||
| + | |||
== TotalView == | == TotalView == | ||
| - | == Sun Studio == | + | == Sun (Oracle Solaris) Studio == |
| + | |||
| + | '' Section contributed by UPB '' | ||
| + | |||
| + | Sun Studio includes a debugger for serial and multithreaded programs. You will find more information on how to use this environment online. You may start debugging your program from Run - Debugg executabile. | ||
| + | |||
| + | There is a series of actions that are available from the Run menu but which may be specified from the command line when starting Sun Studio. In order to just start a debuggind session, you | ||
| + | can attach to a running program by: | ||
| + | |||
| + | $ sunstudio -A pid[:program_name] | ||
| + | |||
| + | or from Run - Attach Debugger. To analyse a core dump, use: | ||
| + | |||
| + | $ sunstudio -C core[:program_name] | ||
| + | |||
| + | or Run - Debug core file. | ||
Latest revision as of 22:56, 20 April 2012
Contents |
Eclipse CDT
Section contributed by IICT-BAS
Eclipse CDT (C/C++ Development Tools) is a Eclipse-based C and C++ IDE. It has a large variety of features including:
- Managed build for various toolchains
- Source navigation
- Source knowledge tools
- Refactoring tools
- Code generation tools
- A variety of debugging tools such as memory, registers and disassembly viewers.
To debug applications using the CDT debugger, you need to build your application in debug mode (using the -g option). To help users familiarized with the Eclipse Debug View, CDT extends it with features for debugging C and C++ code. Using the Debug View, you can manage execution and debugging of programs in the Workbench. Management of breakpoints and variable/registers tracing is all done through the Debug View. The CDT debugger supports debugging for serial and threaded, along with debugging of multiple processes simultaneously, making it a very good tool for many purposes.
The CDT Debug MI plug-in provides support for Machine Interface-compatible debuggers, thus providing the much more reliable MI instead of the more traditional CLI.
Jumpshot
Section contributed by IICT-BAS
SLOG-2 is Argonne Lab's MPI logging package that includes a visualization tool, Jumpshot-4, that allows you to 'see' MPI events in your program and how they relate to time and events in other processes. Jumpshot works by reading a log file that was generated on a run of your MPI program after it has been properly instrumented. Jumpshot-4 allows seamless scrolling from the beginning to the end of the logfile at any zoom level. The main visual component in the SLOG-2 visualization program, Jumpshot-4, is the timeline canvas, which is zoomable and scrollable in both the horizontal and vertical axes. The timeline canvas can be thought of as a timeline vs. time coordinate system. Each point on the canvas is identified by two numbers: a timestamp and a timeline ID. The graphical objects contained in the SLOG-2 file are drawn on the canvas.
TotalView
Sun (Oracle Solaris) Studio
Section contributed by UPB
Sun Studio includes a debugger for serial and multithreaded programs. You will find more information on how to use this environment online. You may start debugging your program from Run - Debugg executabile.
There is a series of actions that are available from the Run menu but which may be specified from the command line when starting Sun Studio. In order to just start a debuggind session, you can attach to a running program by:
$ sunstudio -A pid[:program_name]
or from Run - Attach Debugger. To analyse a core dump, use:
$ sunstudio -C core[:program_name]
or Run - Debug core file.
