I had the same/similar problem. What version of gcc/g++ compiler are you
using? In case of gcc-3.4.x the STL library (libstdc++.so.6) are not
compatible with gcc-3.2/gcc-3.3 (libstdc++.so.5) and intel compiler
seems to have a trouble with resolving this issue. I was able to
succefully build with intel 8.1 + gcc-3.3.x combination and works fine.
It is a bit strange since Intel compiler should be able to support
gcc-3.4. It might be the case for you to have multiple version of gcc's.
Hope this help.
Jim Shepherd wrote:
>On Wed, 2004-12-01 at 13:17 -0500, Jim Shepherd wrote:
>
>
>>received the same results. Here is the debug info:
>>
>> gdb /usr/bin/mpic++
>>GNU gdb Red Hat Linux (6.1post-1.20040607.43rh)
>>Copyright 2004 Free Software Foundation, Inc.
>>GDB is free software, covered by the GNU General Public License, and you
>>are
>>welcome to change it and/or distribute copies of it under certain
>>conditions.
>>Type "show copying" to see the conditions.
>>There is absolutely no warranty for GDB. Type "show warranty" for
>>details.
>>This GDB was configured as "i386-redhat-linux-gnu"...Using host
>>libthread_db library "/lib/tls/libthread_db.so.1".
>>
>>(gdb) run
>>Starting program: /usr/bin/mpic++
>>[Thread debugging using libthread_db enabled]
>>[New Thread -151066944 (LWP 22953)]
>>
>>Program received signal SIGSEGV, Segmentation fault.
>>[Switching to Thread -151066944 (LWP 22953)]
>>0x0804ea6c in lam_wrap_split (str=@0xfefff594, c=32 ' ',
>>out=@0xfefff698) at wrap_cxx.cc:512
>>512 while (i < size && str[i] == c)
>>(gdb) where
>>#0 0x0804ea6c in lam_wrap_split (str=@0xfefff594, c=32 ' ',
>>out=@0xfefff698) at wrap_cxx.cc:512
>>#1 0x0804c2ea in lam_wrap_get_compiler (env_list=@0xfefff7e8,
>>default_comp=@0xfefff818, out=@0xfefff698)
>> at wrap_cxx.cc:165
>>#2 0x0804f778 in lam_wrap_engine (argc=1, argv=0xfefff944,
>>env_vars=@0xfefff7e8, default_compiler=@0xfefff818,
>> want_cxx_includes=true, want_cxx_libs=true, want_f77_includes=false,
>>extra_args=@0xfefff820)
>> at wrap_engine_cxx.cc:68
>>#3 0x08049fa9 in main (argc=1, argv=0xfefff944) at mpicxx.cc:42
>>#4 0x001d8e33 in __libc_start_main () from /lib/tls/libc.so.6
>>#5 0x08049b0d in _start ()
>>(gdb)
>>
>>
>>
>
>I set a breakpoint at the function where the segmentation fault occurs
>and stepped through it until the segmentation fault. Here is the
>output:
>
>(gdb) run
>The program being debugged has been started already.
>Start it from the beginning? (y or n) y
>Starting program: /usr/bin/mpic++
>[Thread debugging using libthread_db enabled]
>[New Thread -151066944 (LWP 22990)]
>[Switching to Thread -151066944 (LWP 22990)]
>
>Breakpoint 1, lam_wrap_split (str=@0xfefff594, c=32 ' ',
>out=@0xfefff698) at wrap_cxx.cc:493
>493 int start, i(0), size(str.size());
>(gdb) step
>494 out.clear();
>(gdb) step
>0x0804ac4a in std::vector<std::string, std::allocator<std::string>
>
>
>>::clear (this=0xfefff698) at stl_vector.h:701
>>
>>
>701 clear() { erase(begin(), end()); }
>(gdb) step
>0x0804a9d2 in std::vector<std::string, std::allocator<std::string>
>
>
>>::begin (this=0xfefff698) at stl_vector.h:314
>>
>>
>314 begin() { return iterator (this->_M_impl._M_start); }
>(gdb) step
>
>Program received signal SIGSEGV, Segmentation fault.
>0x0804b169 in
>_ZN9__gnu_cxx17__normal_iteratorIPSsSt6vectorISsSaISsEEEC9ERKS1_
>(this=0xfefff4cc, __i=@0x1)
> at stl_iterator.h:603
>603 __normal_iterator(const _Iterator& __i) : _M_current(__i)
>{ }
>(gdb)
>
>
>Hope this helps.
>
>-Jim
>
>_______________________________________________
>This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
>
|
