Re: [Boost-users] boost.mpi serialization... error?

Subject: Re: [Boost-users] boost.mpi serialization... error?
From: Andrey Moshbear (andrey.vul_at_[hidden])
Date: 2011-11-01 20:03:22

On Tue, Nov 1, 2011 at 14:31, Jacques C. Richard <richard_at_[hidden]> wrote:
> I am trying boost::mpi on a big code & getting the following error message from mac mpiC++ (same from an intel super-computer). Can anyone pick out something quickly from that to help please or do you need to see more? I'd like to figure out what I did to not do it! :)
> Thanks!
> Jacques
>
> Process=1's mpe_decomp1d MiniGridSize= Â  Â  Â  Â  Â  Â  Â 3 Â  Â  Â  Â  Â  Â  Â  Â 3 Â  Â  Â  Â  Â  Â  Â  Â 3
> Pause @ "main: 879: Domain decomposition" if 1 process: <Enter> or <Return> continues; ^C aborts:
> init_internal_neighbors_wf: Process 1 of 2 exchanging (if necessary) w/+/-1! Sender=1, Receiver=0
> [jacques-richards-mac-mini:00474] *** Process received signal ***
> [jacques-richards-mac-mini:00474] Signal: Segmentation fault (11)
> [jacques-richards-mac-mini:00474] Signal code: Address not mapped (1)
> [jacques-richards-mac-mini:00474] Failing at address: 0x200000001
> [jacques-richards-mac-mini:00474] [ 0] 2   libSystem.B.dylib                   0x00007fff86fa51ba _sigtramp + 26
> [jacques-richards-mac-mini:00474] [ 1] 3 Â  ??? Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  0x0000000000000000 0x0 + 0
> [jacques-richards-mac-mini:00474] [ 2] 4   Mg                                  0x000000010010ff0e _ZN5boost3mpi6detail24ignore_skeleton_oarchiveINS1_16content_oarchiveEE13save_overrideIP12lattice_typeEEvRKT_i + 40
> [jacques-richards-mac-mini:00474] [ 3] 5   Mg                                  0x000000010010ff3a _ZN5boost7archive6detail18interface_oarchiveINS_3mpi6detail16content_oarchiveEElsIKP12lattice_typeEERS5_RT_ + 42
> [jacques-richards-mac-mini:00474] [ 4] 6   Mg                                  0x000000010010ff6e _ZNK5boost13serialization3nvpIKP12lattice_typeE4saveINS_3mpi6detail16content_oarchiveEEEvRT_j + 40
> [jacques-richards-mac-mini:00474] [ 5] 7   Mg                                  0x000000010010ff93 _ZN5boost13serialization6access1
> ...

It would be nice if you used nm -C to get namespace::class::method
instead of gcc's mangled mess.

How do you do this?
$nm -C prog_or_lib | grep $(nm prog_or_lib | grep _Z[gcc mangle] | cut
-d' ' -f1) in terminal.

All I can see is boost::mpi::detail::ignore_skeleton_oarchive followed
by template args and overloads,
boost::archive::detail::interface_oarchive followed by template args
and overloads, and boost::serialization followed by template args and
overloads.
Run nm -C to get human-useful symbol names in the backtrace.