I don't think the "debugger" option to mpirun will work with gdb - I believe it
is intended to work with parallel debuggers such as Totalview. Looking at the
code, I certainly can't see how gdb would work correctly with it.
There is an mpirun option "-xterm" which will launch the xterm windows
automatically for you, but that doesn't resolve your problem as it basically
does what you are doing manually.
It is unclear why you can't run gdb this way on a remote computer. Is something
wrong with xterm? Do you not have an xterm client running on your remote
computer?
On Apr 22, 2010, at 10:05 AM, Немања Илић (Nemanja Ilic) wrote:
> Hello,
>
> I am using Open MPI 1.4.1
>
> Best regards,
> Nemanja Ilic
>
>
> On Thursday 22 April 2010 16:44:13 you wrote:
>> What version of OMPI are you using?
>>
>> On Apr 22, 2010, at 5:11 AM, Немања Илић (Nemanja Ilic) wrote:
>>
>>> Hello,
>>>
>>> I tried to debug with command: "mpirun -debugger gdb -debug -np 4
>>> my_program"
>>> Surely, it starts the debugger, but it doesn't start the debugging nor it
>>> loads any of the my_program threads into the debugger. If I start debugging
>>> manually ("file my_program", then "run"), I can start only one thread of
>>> my_program.
>>> On the contrary when I debug with "mpirun -np 4 xterm -e gdb
>>> my_mpi_application" the four debugger windows are started with separate
>>> thread each, just as it should be.
>>> Since I will be using debugger on a remote computer I can only run gdb in
>>> console mode. Can anyone help me with this?
>>>
>>> Thank you in advance,
>>> Best regards,
>>> Nemanja Ilic
>>> _______________________________________________
>>> users mailing list
>>> us...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>
>>
>
>
>
> _______________________________________________
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
