- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Hello, the following command hangs up on my machine
[linfa@testrun]$ mpirun -gdb -np 3 ../exec/mympiprogram
WARNING: Can't read mpd.hosts for list of hosts, start only on current
Howerver, this run doesn't hang up with the following command
[linfa@testrun]$ mpirun -trace -gdb -np 3 ../exec/mympiprogram
WARNING: Can't read mpd.hosts for list of hosts, start only on current
0: ERROR: ld.so: object 'libVT.so' from LD_PRELOAD cannot be preloaded: ignored.
2: ERROR: ld.so: object 'libVT.so' from LD_PRELOAD cannot be preloaded: ignored.
2: ERROR: ld.so: object 'libVT.so' from LD_PRELOAD cannot be preloaded: ignored.
0: ERROR: ld.so: object 'libVT.so' from LD_PRELOAD cannot be preloaded: ignored.
1: ERROR: ld.so: object 'libVT.so' from LD_PRELOAD cannot be preloaded: ignored.
1: ERROR: ld.so: object 'libVT.so' from LD_PRELOAD cannot be preloaded: ignored.
2: (gdb) 0-1: (gdb) quit
0-2: MPIGDB ENDING
Any ideas? Thanks.
Hello, the following command hangs up on my machine
[linfa@testrun]$ mpirun -gdb -np 3 ../exec/mympiprogram
WARNING: Can't read mpd.hosts for list of hosts, start only on current
Howerver, this run doesn't hang up with the following command
[linfa@testrun]$ mpirun -trace -gdb -np 3 ../exec/mympiprogram
WARNING: Can't read mpd.hosts for list of hosts, start only on current
0: ERROR: ld.so: object 'libVT.so' from LD_PRELOAD cannot be preloaded: ignored.
2: ERROR: ld.so: object 'libVT.so' from LD_PRELOAD cannot be preloaded: ignored.
2: ERROR: ld.so: object 'libVT.so' from LD_PRELOAD cannot be preloaded: ignored.
0: ERROR: ld.so: object 'libVT.so' from LD_PRELOAD cannot be preloaded: ignored.
1: ERROR: ld.so: object 'libVT.so' from LD_PRELOAD cannot be preloaded: ignored.
1: ERROR: ld.so: object 'libVT.so' from LD_PRELOAD cannot be preloaded: ignored.
2: (gdb) 0-1: (gdb) quit
0-2: MPIGDB ENDING
Any ideas? Thanks.
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, I don't have a full answer, but the following suggestions:
The -trace option requests the debug MPI library, which might be helpful when you wish to debug. You might be able to get the same effect by setting LD_PRELOAD to the mpidbg library. Failure to find the trace .so calls into question your installation and mpivars setting for LD_LIBRARY_PATH, but may not stop you from proceeding.
The -trace option requests the debug MPI library, which might be helpful when you wish to debug. You might be able to get the same effect by setting LD_PRELOAD to the mpidbg library. Failure to find the trace .so calls into question your installation and mpivars setting for LD_LIBRARY_PATH, but may not stop you from proceeding.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi linfa,
Please do not use -trace and -gdb option together.
-trace option is used to collect information about MPI communications in your program. Once you get a trace file you can analyze it in Intel Trace Analyzer (traceanalyzer). Of cause you need to have this product.
If you use -trace together with -gdb your trace files will be useless. Also trace library inserts own functions, so debugging of such application will be useless as well.
Regards!
Dmitry
Please do not use -trace and -gdb option together.
-trace option is used to collect information about MPI communications in your program. Once you get a trace file you can analyze it in Intel Trace Analyzer (traceanalyzer). Of cause you need to have this product.
If you use -trace together with -gdb your trace files will be useless. Also trace library inserts own functions, so debugging of such application will be useless as well.
Regards!
Dmitry
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page