Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   26626 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

MPE_Errors_call_debugger(4)	      MPE	   MPE_Errors_call_debugger(4)

NAME
       MPE_Errors_call_debugger	 -  On an error, print a message and (attempt)
       to start the specified debugger on the program

SYNOPSIS
       void MPE_Errors_call_debugger( pgm, dbg, args )
       char *pgm, *dbg, **args;

INPUT PARAMETERS
       pgm    - Name of the program.
       dbg    - Name of the debugger.  If null, use a default (usually dbx)
       args   - arguments to use in  generating	 the  debugger.	  This	allows
	      things like "'xterm -e dbx pgm pid'", or "'xdbx -geometry +%d+%d
	      pgm pid'".  The list should be null terminated.	(The  '%d  %d'
	      format is not yet supported).

NOTES
       You  may need to ignore some signals, depending on the signals that the
       MPICH and underlying communications code is using.  You can do this  in
       dbx by adding "ignore signal-name" to your .dbxinit file.  For example,
       to ignore 'SIGUSR1', use "'ignore USR1'".

       Currently, there is no Fortran interface for this routine.

LOCATION
				   3/24/2011	   MPE_Errors_call_debugger(4)

Vote for polarhome