[mpich-discuss] debugging with idb or gdb

[Peter Brady]

Hello all,

I am trying to debug a program compiled with ifort and the latest mpich2
libraries.  I have two issues:

1.  While I can launch gdb with the -gdb option from mpiexec, gdb has the
unfortunate inability to read data from fortran modules other than the one
it's currently in.  I've googled around for an answer but haven't found one
yet.  Does anyone know how do this in gdb?

2.  I've tried to use idb (which can access data from other fortan modules)
but I can't seem to get it to work with mpi.  I've done

> mpiexec -n 2 idb -parallel ./program

and I've tried attaching it to a running program but I just get the same
errors:

> Intel(R) Debugger for applications running on Intel(R) 64, Version 10.1-35
> , Build 20080310
> Reading symbols from
> /home/peter/runs/lidDrivenCavity/wall_xp/128/test/arts...Reading symbols
> from /home/peter/runs/lidDrivenCavity/wall_xp/128/test/arts...done.
> done.
> Assertion failed: falsesrc/appl/procs/parallel/parallelSupport.C333
> This isA an unexpected condition and may indicate the presence of a defect.
> If you wish to report this, please include the stack trace that follows.
> ssertion failed: falsesrc/appl/procs/parallel/parallelSupport.C333
> This is an unexpected condition and may indicate the presence of a defect.
> If you wish to report this, please include the stack trace that follows.
> /opt/intel/idbe/10.1.017/bin/idb-e(_ZN15IDBAssertFailed3runEPKcS1_j+0xe)
> [0xcb304c]
> /opt/intel/idbe/10.1.017/bin/idb-e(_ZN15IDBAssertFailed3runEPKcS1_j+0xe)
> [0xcb304c]
> /opt/intel/idbe/10.1.017/bin/idb-e(_ZN14DTLU_namespace12assertFailedEPKcS1_j+0x24)
> [0xf1c38c]
> /opt/intel/idbe/10.1.017/bin/idb-e(_Z19makeParallelSessionv+0x25c)
> [0xe3c6d0]
> /opt/intel/idbe/10.1.017/bin/idb-e(_ZN14DTLU_namespace12assertFailedEPKcS1_j+0x24)
> [0xf1c38c]
> /opt/intel/idbe/10.1.017/bin/idb-e(_Z19makeParallelSessionv+0x25c)
> [0xe3c6d0]
> /opt/intel/idbe/10.1.017/bin/idb-e(_Z15decladebug_initiPPKcS1_+0x78b)
> [0xcb1ba9]
> /opt/intel/idbe/10.1.017/bin/idb-e(_Z7idbMainiPPKcS1_+0x60e) [0xcaf2de]
> /opt/intel/idbe/10.1.017/bin/idb-e(main+0x3c) [0xb87a98]
> /lib64/libc.so.6(__libc_start_main+0xf4) [0x352041e074]
> /opt/intel/idbe/10.1.017/bin/idb-e(_ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_c+0x5a)
> [0x7ba02a]
> /opt/intel/idbe/10.1.017/bin/idb-e(_Z15decladebug_initiPPKcS1_+0x78b)
> [0xcb1ba9]
> /opt/intel/idbe/10.1.017/bin/idb-e(_Z7idbMainiPPKcS1_+0x60e) [0xcaf2de]
> /opt/intel/idbe/10.1.017/bin/idb-e(main+0x3c) [0xb87a98]
> /lib64/libc.so.6(__libc_start_main+0xf4) [0x352041e074]
> /opt/intel/idbe/10.1.017/bin/idb-e(_ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_c+0x5a)
> [0x7ba02a]
>
>
> Intel(RIn) Debugger for applications running on Intel(R) 64, Version
> 10.1-35  caught signal "Aborted" (6).
> This is an unexpected condition and may indicate the presence of a defect.
> If you wish to report this, please include the stack trace that follows.
> tel(R) Debugger for appli/lib64/libc.so.6 [0x3520430f30]
> /lib64/libc.so.6(gsignal+0x35) [0x3520430ec5]
> /lib64/libc.so.6(abort+0x110) [0x3520432970]
> /usr/lib64/libstdc++.so.5 [0x7fc1ef44c086]
> /usr/lib64/libstdc++.so.5 [0x7fc1ef44c0c3]
> /usr/lib64/libstdc++.so.5 [0x7fc1ef44c1e3]
> /opt/intel/idbe/10.1.017/bin/idb-e(deb_assert+0x75) [0xcdc991]
> /opt/intel/idbe/10.1.017/bin/idb-e(_ZN15IDBAssertFailed3runEPKcS1_j+0xe)
> [0xcb304c]
> /opt/intel/idbe/10.1.017/bin/idb-e(_ZN14DTLU_namespace12assertFailedEPKcS1_j+0x24)
> [0xf1c38c]
> /opt/intel/idbe/10.1.017/bin/idb-e(_Z19makeParallelSessionv+0x25c)
> [0xe3c6d0]
> /opt/intel/idbe/10.1.017/bin/idb-e(_Z15decladebug_initiPPKcS1_+0x78b)
> [0xcb1ba9]
> /opt/intel/idbe/10.1.017/bin/idb-e(_Z7idbMainiPPKcS1_+0x60e) [0xcaf2de]
> /opt/intel/idbe/10.1.017/bin/idb-e(main+0x3c) [0xb87a98]
> /lib64/libc.so.6(__libc_start_main+0xf4) [0x352041e074]
> /opt/intel/idbe/10.1.017/bin/idb-e(_ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_c+0x5a)
> [0x7ba02a]
> cations running on Intel(R) 64, Version 10.1-35  caught signal "Aborted"
> (6).
> This is an unexpected condition and may indicate the presence of a defect.
> If you wish to report this, please include the stack trace that follows.
> /lib64/libc.so.6 [0x3520430f30]
> /lib64/libc.so.6(gsignal+0x35) [0x3520430ec5]
> /lib64/libc.so.6(abort+0x110) [0x3520432970]
> /usr/lib64/libstdc++.so.5 [0x53ca086]
> /usr/lib64/libstdc++.so.5 [0x53ca0c3]
> /usr/lib64/libstdc++.so.5 [0x53ca1e3]
> /opt/intel/idbe/10.1.017/bin/idb-e(deb_assert+0x75) [0xcdc991]
> /opt/intel/idbe/10.1.017/bin/idb-e(_ZN15IDBAssertFailed3runEPKcS1_j+0xe)
> [0xcb304c]
> /opt/intel/idbe/10.1.017/bin/idb-e(_ZN14DTLU_namespace12assertFailedEPKcS1_j+0x24)
> [0xf1c38c]
> /opt/intel/idbe/10.1.017/bin/idb-e(_Z19makeParallelSessionv+0x25c)
> [0xe3c6d0]
> /opt/intel/idbe/10.1.017/bin/idb-e(_Z15decladebug_initiPPKcS1_+0x78b)
> [0xcb1ba9]
> /opt/intel/idbe/10.1.017/bin/idb-e(_Z7idbMainiPPKcS1_+0x60e) [0xcaf2de]
> /opt/intel/idbe/10.1.017/bin/idb-e(main+0x3c) [0xb87a98]
> /lib64/libc.so.6(__libc_start_main+0xf4) [0x352041e074]
> /opt/intel/idbe/10.1.017/bin/idb-e(_ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_c+0x5a)
> [0x7ba02a]

I've googled around for this error message as well and no one seems to have
a response to it.  Any ideas?

Thanks in advance,
Peter.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20080903/a28059c9/attachment.htm>