Pgdbg/en: Difference between revisions

Jump to navigation Jump to search
Updating to match new version of source page
(Updating to match new version of source page)
 
(Updating to match new version of source page)
Line 1: Line 1:
<languages />
<languages />
= Description =
PGDBG is a powerful and simple tool for debugging both MPI-parallel and OpenMP thread-parallel Linux applications. It is included in the PGI compiler package and configured for OpenMP thread-parallel debugging.
PGDBG is a powerful and simple tool for debugging both MPI-parallel and OpenMP thread-parallel Linux applications. It is included in the PGI compiler package and configured for OpenMP thread-parallel debugging.


For the most of the C, C++, or Fortran 77 codes one can use a regular GNU debugger such as GDB. However, the Fortran 90/95 programs are not handled very well by the GDB. The Portland Group has developed a debugger called [https://www.pgroup.com/products/tools.htm/pgdbg.htm pgdbg]  which is more suited for such codes. Pgdbg is provided in two modes: a graphical mode with the enabled X11 forwarding or a text mode.  
For the most of the C, C++, or Fortran 77 codes one can use a regular GNU debugger such as GDB. However, the Fortran 90/95 programs are not handled very well by the GDB. The Portland Group has developed a debugger called [https://www.pgroup.com/products/tools.htm/pgdbg.htm pgdbg]  which is more suited for such codes. Pgdbg is provided in two modes: a graphical mode with the enabled X11 forwarding or a text mode.  


= Quickstart guide =  
= Quickstart guide =
Using PGDBG usually consists of two steps:
Using PGDBG usually consists of two steps:
# '''Compilation''': Compile the code with the debugging enabled
# '''Compilation''': Compile the code with the debugging enabled
Line 24: Line 25:
{{Command|pgcc -g program.c -o program}}
{{Command|pgcc -g program.c -o program}}


== Command-line mode ==  
== Command-line mode ==
Once your code is compiled with the proper options, you can run the PGDBG for the analysis. The debugger's default user interface is a graphical user interface or GUI. However, if for some reasons you don't want to run in GUI or don't have X11 forwarding, you can run pgdbg in a text mode by adding an extra option "-text" :
Once your code is compiled with the proper options, you can run the PGDBG for the analysis. The debugger's default user interface is a graphical user interface or GUI. However, if for some reasons you don't want to run in GUI or don't have X11 forwarding, you can run pgdbg in a text mode by adding an extra option "-text" :
{{Command|pgdbg -text program arg1 arg2}}
{{Command|pgdbg -text program arg1 arg2}}
Line 100: Line 101:
=== Debug information tab ===
=== Debug information tab ===
Debug information tabs take up the lower half of the debugger GUI. Each of these tabs provides a particular function or view of debug information. The following sections discuss the tabs as they appear from left-to-right in the GUI’s default configuration.
Debug information tabs take up the lower half of the debugger GUI. Each of these tabs provides a particular function or view of debug information. The following sections discuss the tabs as they appear from left-to-right in the GUI’s default configuration.
= References =
* [https://www.pgroup.com/resources/docs/17.7/x86/pgdbg-user-guide/index.htm PGI Debugger User's Guide]
* [https://www.pgroup.com/index.htm PGI webpage]
38,897

edits

Navigation menu