<div>I do not have acess to linux right now, I will check it as the first thing tomorrow.</div>
<div> </div>
<div>Yan<br><br></div>
<div class="gmail_quote">On Sun, Jul 19, 2009 at 12:54 AM, Barry Smith <span dir="ltr"><<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br> Are you sure the other window isn't lurking away somewhere off (or nearly) off the screen?<br><br>
Maybe try shutting down the x server and restarting?<br><font color="#888888"><br> Barry</font>
<div>
<div></div>
<div class="h5"><br><br>On Jul 18, 2009, at 11:50 PM, Ryan Yan wrote:<br><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Thank you very much, Barry.<br><br>After I use the vyan2000-linux:0.0, I got errors without any gdb window.<br>
<br>vyan2000@vyan2000-linux:~/local/PPETSc/petsc-2.3.3-p15/src/ksp/ksp/examples/tutorials/ttt2$ mpirun -np 2 ./rpisolve -ksp_monitor_true_residual -start_in_debugger -display vyan2000-linux:0.0<br>[0]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve of pid 26518 on display vyan2000-linux:0.0 on machine vyan2000-linux<br>
[1]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve of pid 26519 on display vyan2000-linux:0.0 on machine vyan2000-linux<br>xterm Xt error: Can't open display: vyan2000-linux:0.0<br>xterm Xt error: Can't open display: vyan2000-linux:0.0<br>
<br>Then<br>I changed back,<br>vyan2000@vyan2000-linux:~/local/PPETSc/petsc-2.3.3-p15/src/ksp/ksp/examples/tutorials/ttt2$ mpirun -np 2 ./rpisolve -ksp_monitor_true_residual -start_in_debugger -display :0.0<br><br>Same as before, error messages with only a single gdb window, (and the window shows up at different place at different instances).<br>
<br>Yan<br><br><br>On Sun, Jul 19, 2009 at 12:30 AM, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>> wrote:<br><br> Try using -display vyan2000-linux:0.0<br><br> Shouldn't make any difference but since it appears you are running everything on the same machine what you have given should work.<br>
<br> Barry<br><br><br>On Jul 18, 2009, at 11:24 PM, Ryan Yan wrote:<br><br>Hi All,<br>I am tring to use the PETSc runtime option -start_in_debugger.<br><br>However, when I attach the debugger at run time to each process, there are error messages and I only get one gdb window(Am I suppose to get as many as the number of the processes?)<br>
<br>vyan2000@vyan2000-linux:~/local/PPETSc/petsc-2.3.3-p15/src/ksp/ksp/examples/tutorials/ttt2$ mpirun -np 2 ./rpisolve -ksp_monitor_true_residual -start_in_debugger -display :0.0<br><br>[1]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve of pid 26307 on display :0.0 on machine vyan2000-linux<br>
[0]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve of pid 26306 on display :0.0 on machine vyan2000-linux<br><br>Then, only a *single* gdb window prompts out. When I run with 3 process, there are only *two* gdb windows.<br>
<br>Thank you very much in advance,<br><br>Yan<br><br><br></blockquote><br></div></div></blockquote></div><br>