[mpich-discuss] A issue while running an application with mpich2

[Balaji, Pavan]

That's a generic error message saying, well, something is wrong with your application.

The only additional piece of information is that the exit code is 134, which is actually a signal (128 + 6, where "6" is the signal code == SIGABRT).  Meaning, your application aborted with the SIGABRT signal.  Here's some information from our stackoverflow friends:

http://stackoverflow.com/questions/3413166/when-does-a-process-get-sigabrt-signal-6

This has nothing to do with MPICH or MPI.  You need to debug your application.

  -- Pavan

> On Jan 16, 2016, at 4:22 AM, 20122009刘琛 <13630583107 at 163.com> wrote:
> 
> I have this issue while running an benchmark with mpich2 ,but it always ended up like the picture<QQ20160116-0.png><QQ20160116-1.png>
> what is wrong with my application?I am new to MPICH2.
> This is  the command I used :
> mpirun -f machine_file -n 4 ./filename and other benchmark-specified params.
> machine_file contains  an IP ,which is my computer's IP.
> Thanks for your help!
> 
> 
> 新的一年，让我陪你奋斗，让我陪你辛苦！-2016携手前行>>
> 
> 
> 
> 新的一年，让我陪你奋斗，让我陪你辛苦！-2016携手前行>>
> 
> <QQ20160116-0.png><QQ20160116-1.png>_______________________________________________
> discuss mailing list     discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss

_______________________________________________
discuss mailing list     discuss at mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss