<div class="gmail_quote">On Wed, Jan 25, 2012 at 15:28, Dominik Szczerba <span dir="ltr"><<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":1wy">It will take several minutes till xterm gdb windows will pop up, till<br>
I will manage to type "c+ENTER" into 64 windows on my 1024x768<br>
quadcore, and then till I find the right window where the executions<br>
stopped - but yes, it is definitely doable, and I already did that, as<br>
posted separately.</div></blockquote></div><br><div>Why do you have to run on 64 processes to find out if ParMETIS is called? Are you worried that there is code in PETSc that says</div><div><br></div><div>if (comm_size >= 64) do_crazy_things();</div>
<div><br></div><div><br></div><div>So run on a small number of processes (like 2 or 4) to see who calls ParMETIS.</div><div><br></div><div><br></div><div>You can batch up setting of breakpoints</div><div><br></div><div>mpiexec -n 4 xterm -e gdb -ex 'b file.c:42' -ex r --args ./app -options -for_petsc</div>
<div><br></div><div><br></div><div>These will run until they hit the breakpoint, no need to press "c".</div><div><br></div><div><br></div><div>If a partitioner is called to partition a global problem, then all ranks must call it. In the case of ParMETIS errors, the output you showed told you the rank. Suppose you want to look at ranks 13 and 59 of a 64-process job.</div>
<div><br></div><div>run="./app -options -for_petsc"</div><div>dbg="xterm -e gdb -ex 'b file.c:42' -ex r --args $run"</div><div>mpiexec -n 13 $run : -n 1 $dbg : -n 45 $run : -n 1 $dbg : -n 4 $run</div>