illegal instruction (CPU mismatch)

Mahmood Naderan nt_mahmood@yahoo.com
Fri Sep 16 12:12:00 GMT 2016


Markus,
I ran "set follow-fork-mode child" on another terminal while I was connecting to the compute node. Please see the output of the gdb

$ gdb --args /share/apps/siesta/openmpi-2.0.0/bin/mpirun -hostfile hosts.txt -np 15 sc.sh
Reading symbols from /share/apps/siesta/openmpi-2.0.0/bin/mpirun...done.
(gdb) run
Starting program: /share/apps/siesta/openmpi-2.0.0/bin/mpirun -hostfile hosts.txt -np 15 sc.sh
[Thread debugging using libthread_db enabled]
[New Thread 0x2aaaaafcc700 (LWP 26346)]
[New Thread 0x2aaaab1cd700 (LWP 26347)]
[New Thread 0x2aaaab3ce700 (LWP 26348)]
[New Thread 0x2aaaab5cf700 (LWP 26349)]
Detaching after fork from child process 26350.

...
...
--------------------------------------------------------------------------
mpirun noticed that process rank 0 with PID 16401 on node compute-0-1 exited on signal 4 (Illegal instruction).
--------------------------------------------------------------------------
[Thread 0x2aaaab5cf700 (LWP 26349) exited]
[Thread 0x2aaaab3ce700 (LWP 26348) exited]
[Thread 0x2aaaab1cd700 (LWP 26347) exited]
[Thread 0x2aaaaafcc700 (LWP 26346) exited]

Program exited with code 0204.
Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.80.el6_3.6.x86_64 libibverbs-1.1.8-4.el6.x86_64 libnl-1.1-14.el6.x86_64 libudev-147-2.42.el6.x86_64
(gdb) disas
No frame selected.
(gdb)




This time the output has some more lines, so I think the "follow-fork-module" worked. But still the process is dead!


Regards,
Mahmood



More information about the Gcc-help mailing list