topic hi Taylor thanks for the in Software Archive

debugging remotely on MIC

VIKRANT_G_ — Mon, 10 Feb 2014 00:26:09 GMT

Hello,

I am trying to run gdb on the mic and i get the following error:

HYDU_create_process (./utils/launch/launch.c:111): execvp error on file /tmp/gdb (No such file or directory)

but i did copy the gdb on mic using--> scp /usr/linux-k1om-4.7/linux-k1om/usr/bin/gdb mic0:/tmp"

also i followed the steps on http://software.intel.com/en-us/articles/debugging-intel-xeon-phi-applications-on-linux-host, in one section it mentions about debugging remotely and uses $ scp <composer_xe_root>/debugger/gdb/target/mic/bin/gdbserver mic0:/tmp

but i tried to find a directory /debugger/gdb/,..in my computer but it seems there is no such directory,

(I can successfully run gdb on xeon processor,)

thank you for the help in advance

That's a MIC native debugger.

TimP — Mon, 10 Feb 2014 02:35:00 GMT

That's a MIC native debugger. If you copy it over to mic0:/bin it will run a native application in a shell on mic.

The gdbserver would come in the (optional) debugger installation with the Intel Fortran or C++ compiler

hello Tim,

VIKRANT_G_ — Mon, 10 Feb 2014 16:24:49 GMT

hello Tim,

i do have a gdbserver but the directory is different from what is mentioned in the link(for MIC debugging). So when i provide the gdb server directory i still cannot use gdb remotely on MIC.

Yeah you are right, i can debug native application on MIC, the problem i get is when i try to use gdb remotely

hello , i changed my approach

VIKRANT_G_ — Tue, 11 Feb 2014 19:51:59 GMT

hello , i changed my approach and switched to idb_debugger which is running fine through remote debugging,

but i have another issue: I am trying to run two programs simultaneously one on MIC and one on Xeon, it involves handshake between the two.

the issue i face is : I need to run both the exes simultaneously for program to work. I need to debug the MIC program while the program is running.

this is the command i am using currently:

mpirun -host mic0 -n 1 ~/hello.mic: -host localhost -n 1 ./hello.xeon, how do i add a debug option in this command,

Hi Vikrant,

TaylorIoTKidd — Fri, 14 Feb 2014 21:04:53 GMT

Hi Vikrant,

Consulting with some MPI experts here, they suggest two methods for debugging. The first is to set, using -genv, the I_MPI_DEBUG variable. See section 2.5.1.5, "Environmental Variables", in the Intel(r) MPI Library for Linux* OS Reference Manual. This gives you debug information related to the MPI Library.

mpirun –genv I_MPI_DEBUG 3 -host mic0 -n 1 ~/hello.mic: -host localhost -n 1 ./hello.xeon

Another suggestion is to use the -v option which gives you debug information about the MPI process manager. See section 2.3.1.3 in the same document.

Regards
--
Taylor

Try adding -gdb to your

Gregg_S_Intel — Fri, 14 Feb 2014 21:43:16 GMT

Try adding -gdb to your mpirun command.

mpirun -gdb -host mic0 -n 1 ./hello.mic: -host localhost -n 1 ./hello.xeon

mpigdb: np = 2
mpigdb: attaching to 185758 ./hello.xeon localhost
mpigdb: attaching to 37159 ./hello.mic mic0
[0,1] (mpigdb)

hi Taylor thanks for the

VIKRANT_G_ — Fri, 14 Feb 2014 22:07:30 GMT

hi Taylor thanks for the debug option, I tried it but i get some library issues,

hi Gregg i did put -gdb and heres what i got:

mpirun -gdb -host mic0 -n 1 ~/hello.mic : -host localhost -n 1 ./hello.xeon
mpigdb: np = 2
mpigdb: attaching to 4397 /root/hello.mic mic0
mpigdb: hangup detected: while read from [0]
mpigdb: attaching to 10995 ./hello.xeon localhost
[0,1] (mpigdb)

now i tried running it like how i debug in gdb by putting break point

"(mpigdb) break main" but the program just stood there does nothing

Hi Vikrant,

Gergana_S_Intel — Mon, 24 Feb 2014 22:54:22 GMT

Hi Vikrant,

I assume you're running the Intel® MPI Library here? Do you know what version?

Using the -gdb option should be what enables the GNU debugger with Intel MPI. Can you tell me if your original mpirun job (without -gdb) finishes successfully?

Alternatively, you can attach to a running process via the "-gdba <pid>" option, like this:

$ mpirun -gdba <pid>

Perhaps you can start the job first, then attach to the rank you want to debug this way.

Regards,
~Gergana