PETSC debugger

[Ryan Yan]

Thank you very much, barry,

Only debugging one processes is a way to go for my current bug(s).

Yan

On Sun, Jul 19, 2009 at 5:00 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:

>
>   This option works by starting up an xterm with gdb running in that xterm.
> The code is in src/sys/error/adebug.c
>
>   If you only need to look at one process, you can use the options
> -start_in_debugger noxterm -debugger_nodes 0 (or 1 or 2) then all the other
> processes won't use the debugger.
>
>   Barry
>
>
>
>
> On Jul 19, 2009, at 3:49 PM, Ryan Yan wrote:
>
>  Hi Barry,
>> I restarted x server many times(during turning off the option as )
>> -nolisten tcp as Berend. And I also checked very carefully each time the
>> bottom margin of the window status panel. The gdb window did not function
>> correctly on my Linux box. Thanks in advance for any suggestions
>>
>>
>>
>> On Sun, Jul 19, 2009 at 12:54 AM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>>
>>  Are you sure the other window isn't lurking away somewhere off (or
>> nearly) off the screen?
>>
>>  Maybe try shutting down the x server and restarting?
>>
>>  Barry
>>
>>
>> On Jul 18, 2009, at 11:50 PM, Ryan Yan wrote:
>>
>> Thank you very much, Barry.
>>
>> After I use the vyan2000-linux:0.0, I got errors without any gdb window.
>>
>> vyan2000 at 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
>> [0]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve of pid 26518 on display
>> vyan2000-linux:0.0 on machine vyan2000-linux
>> [1]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve of pid 26519 on display
>> vyan2000-linux:0.0 on machine vyan2000-linux
>> xterm Xt error: Can't open display: vyan2000-linux:0.0
>> xterm Xt error: Can't open display: vyan2000-linux:0.0
>>
>> Then
>> I changed back,
>> vyan2000 at 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
>>
>> Same as before, error messages with only a single gdb window, (and the
>> window shows up at different place at different instances).
>>
>> Yan
>>
>>
>> On Sun, Jul 19, 2009 at 12:30 AM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>>
>>  Try using -display vyan2000-linux:0.0
>>
>>  Shouldn't make any difference but since it appears you are running
>> everything on the same machine what you have given should work.
>>
>>  Barry
>>
>>
>> On Jul 18, 2009, at 11:24 PM, Ryan Yan wrote:
>>
>> Hi All,
>> I am tring to use the PETSc runtime option -start_in_debugger.
>>
>> 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?)
>>
>> vyan2000 at 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
>>
>> [1]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve of pid 26307 on display
>> :0.0 on machine vyan2000-linux
>> [0]PETSC ERROR: PETSC: Attaching gdb to ./rpisolve of pid 26306 on display
>> :0.0 on machine vyan2000-linux
>>
>> Then, only a *single* gdb window prompts out. When I run with 3 process,
>> there are only *two* gdb windows.
>>
>> Thank you very much in advance,
>>
>> Yan
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20090719/8f659899/attachment.htm>