Dear Berend,<br>Thanks for your suggestion. I can see that option right there!!<br><br>However, I am still struggling to find a way to turn this option off as I can see from <br><br>vyan2000@vyan2000-linux:/etc/gdm$ ps -ef | grep /usr/bin/X<br>
root 5287 5285 3 14:19 tty7 00:00:42 /usr/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7<br><br>I am using Ubuntu *gnome*, but there is no such gdmrc file that I can correct. I tried several other ways, but have not succeed yet.<br>
vyan2000@vyan2000-linux:/etc/gdm$ uname -a<br>Linux vyan2000-linux 2.6.24-24-generic #1 SMP Tue Jul 7 19:46:39 UTC 2009 i686 GNU/Linux<br><br>I am still searching....<br><br>Regards,<br><br>Yan <br><br><br><div class="gmail_quote">
On Sun, Jul 19, 2009 at 2:59 AM, Berend van Wachem <span dir="ltr"><<a href="mailto:b.van-wachem@imperial.ac.uk">b.van-wachem@imperial.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dear Ryan,<br>
<br>
I had a similar issue as you have. I am using KDE as a desktop manager and found that I have to comment out the line<br>
<br>
"ServerArgsLocal=-nolisten tcp"<br>
<br>
in kdm, in the kdmrc file (on my system located at /etc/kde/kdm/kdmrc).<br>
<br>
After restarting kdm, I get all windows of gdb coming up.<br>
<br>
Regards,<br>
<br>
Berend.<br>
<br>
<br>
Ryan Yan wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
I do not have acess to linux right now, I will check it as the first thing tomorrow.<br>
Yan<br>
<br></div><div><div></div><div class="h5">
On Sun, Jul 19, 2009 at 12:54 AM, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a> <mailto:<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>>> wrote:<br>
<br>
<br>
Are you sure the other window isn't lurking away somewhere off (or<br>
nearly) off the screen?<br>
<br>
Maybe try shutting down the x server and restarting?<br>
<br>
Barry<br>
<br>
<br>
On Jul 18, 2009, at 11:50 PM, Ryan Yan wrote:<br>
<br>
Thank you very much, Barry.<br>
<br>
After I use the vyan2000-linux:0.0, I got errors without any gdb<br>
window.<br>
<br>
vyan2000@vyan2000-linux:~/local/PPETSc/petsc-2.3.3-p15/src/ksp/ksp/examples/tutorials/ttt2$<br>
mpirun -np 2 ./rpisolve -ksp_monitor_true_residual<br>
-start_in_debugger -display vyan2000-linux:0.0<br>
[0]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve of pid 26518<br>
on display vyan2000-linux:0.0 on machine vyan2000-linux<br>
[1]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve of pid 26519<br>
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$<br>
mpirun -np 2 ./rpisolve -ksp_monitor_true_residual<br>
-start_in_debugger -display :0.0<br>
<br>
Same as before, error messages with only a single gdb window,<br>
(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<br></div></div><div class="im">
<<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a> <mailto:<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<br>
running everything on the same machine what you have given<br>
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,<br>
there are error messages and I only get one gdb window(Am I<br>
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$<br>
mpirun -np 2 ./rpisolve -ksp_monitor_true_residual<br>
-start_in_debugger -display :0.0<br>
<br>
[1]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve of pid 26307<br>
on display :0.0 on machine vyan2000-linux<br>
[0]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve of pid 26306<br>
on display :0.0 on machine vyan2000-linux<br>
<br>
Then, only a *single* gdb window prompts out. When I run with 3<br>
process, there are only *two* gdb windows.<br>
<br>
Thank you very much in advance,<br>
<br>
Yan<br>
<br>
<br>
<br>
<br>
</div></blockquote>
</blockquote></div><br>