PETSC debugger

[Jed Brown]

Ryan Yan wrote:
> My X server set up may be messed up somehow. Same error as before.

Using screen bypasses X, so that seems an unlikely candidate.

> After I creat a new session using,
> vyan2000 at vyan2000-linux:~/local/PPETSc/petsc-2.3.3-p15/src/ksp/ksp/examples/tutorials/ttt2$
> screen -S sdebug
> 
> Still errors.

No errors at this point though, right?

> vyan2000 at vyan2000-linux:~/local/PPETSc/petsc-2.3.3-p15/src/ksp/ksp/examples/tutorials/ttt2$
> mpirun -n 4 ./rpisolve -start_in_debugger -debug_terminal "screen -S sdebug
> -X screen"
> [0]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve on pid 9758 on
> vyan2000-linux
> [1]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve on pid 9755 on
> vyan2000-linux
> [3]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve on pid 9757 on
> vyan2000-linux
> [2]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve on pid 9756 on
> vyan2000-linux
> 
> The number of the screen for gdb is not equal to the number of
> processes.(Mostly, less than), as you can see in the following "bottom
> margin" of my screen session.

Are there *ever* more sessions than the number of processes?  Are there
ever the same number?  Is there any consistency to which process is
missing?  The output above indicates that the debugger is being run and,
from the perspective of PetscAttachDebugger, the operation was
successful.  I have seen this behavior (one missing debug session) on a
couple occasions, but it wasn't reproducible so I couldn't debug it.  If
this continues to be a problem, I recommend attaching the debugger
yourself (put "set breakpoint pending on" and "break PetscError" in your
.gdbinit or run with -on_error_abort).

Jed

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20090720/0f218dd9/attachment.pgp>