Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What does PGDBG do differently when the MPIRUN -nolocal option is used?

mpirun option pgdbg Used
0
Posted

What does PGDBG do differently when the MPIRUN -nolocal option is used?

0

When PGDBG is invoked using MPIRUN without ‘-nolocal’, the target application processes are spawned on the local host as well as on remote hosts. The debugger is launched on the local host, and a lightweight debug server (named ‘pgserv’) is launched on every host where a target process is running (both local and remote). When PGDBG is invoked using MPIRUN with ‘-nolocal’, the target application processes are spawned only on remote hosts, as determined by the ‘machines.LINUX’ file. The debugger is launched on the local host, and pgserv is launched only on the hosts where target processes are running (i.e. only on remote hosts). This allows the debugger to be isolated from the application under debug, in order to (for example) prevent resource contention between the debugger and the application.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123