Charm++ parallel programming system

[Gengbin Zheng <zhenggb AT gmail.com>]

Hi Jim,

 If you compile charm/AMPI and test code with -g, you can get stack
trace with command:   addr2line

 Could you also please send us your test program? We can take a look here.

Gengbin

On Wed, Jul 13, 2011 at 9:34 PM, Jim Edwards 
<jedwards AT ucar.edu>
 wrote:
> I've now built the AMPI_ROMIO and am trying a very simple MPI IO program.
> It dies in the call to MPI_FILE_OPEN although it does manage to create a 0
> length file first.
>
> What can I do to get a more meaningful stack traceback?
>
> Charm++> Running on MPI version: 2.1 multi-thread support: 0 (max supported:
> -1)
> Charm++> Running on 1 unique compute nodes (12-way SMP).
>  testmpiio2.F90          64           1
>  testmpiio2.F90          64           1
> ------------- Processor 0 Exiting: Caught Signal ------------
> Signal: 11
> ------------- Processor 1 Exiting: Caught Signal ------------
> Signal: 11
> [1] Stack Traceback:
>   [1:0] [0x587570]
>   [1:1] [0x530e7f]
>   [1:2] [0x52fbaa]
>   [1:3] [0x50cce5]
>   [1:4] [0x400b5d]
>   [1:5] [0x404b83]
>   [1:6] [0x429677]
>   [1:7] [0x404ed3]
>   [1:8] [0x43c0cf]
>   [1:9] [0x442d39]
>   [1:10] [0x4dd270]
>   [1:11] [0x4dd35e]
> _pmii_daemon(SIGCHLD): [NID 00063] PE 0 exit signal Segmentation fault
> [NID 00063] 2011-07-13 20:27:12 Apid 157307: initiated application
> termination
> Application 157307 exit codes: 139
> Application 157307 resources: utime 0, stime 0
>
>
> _______________________________________________
> ppl mailing list
> ppl AT cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/ppl
>
>