[mpich-discuss] MPICH2 logging on windows

bruno.guerraz at orange.com bruno.guerraz at orange.com
Wed Jun 5 02:15:15 CDT 2013


Here is attached a simple test. This is a simple Master/Slave program. 
The master launches several slaves with MPI_Comm_spawn.
I run the program with the command line mpiexec.exe  -log -n 1  -localonly master.exe
With or without the lines MPE_Init_log(); and MPE_Finalize_log() it fails with the same error 

.\src\logging\src\clog_commset.c:CLOG_CommSet_get_IDs() - 
	PMPI_Comm_get_attr() fails!
Backtrace of the callstack at rank 0:
unable to read the cmd header on the pmi context, Error = -1

thanks in advance
Bruno
-----Message d'origine-----
De : Jayesh Krishna [mailto:jayesh at mcs.anl.gov] 
Envoyé : mardi 4 juin 2013 16:48
À : discuss at mpich.org
Cc : GUERRAZ Bruno OLNC/OLPS
Objet : Re: [mpich-discuss] MPICH2 logging on windows

Hi,
 Can you send us a simple test case (extracted from your code) that fails?

Regards,
Jayesh

----- Original Message -----
From: "bruno guerraz" <bruno.guerraz at orange.com>
To: discuss at mpich.org
Sent: Tuesday, June 4, 2013 5:10:49 AM
Subject: [mpich-discuss] MPICH2 logging on windows





Hi, 

I try to use MPE logging on my mpi program on Windows. 

It works fine on the cpi example. 

I have only linked my program with mpe.lib and run on a single machine with –localonly –log options. I use dynamic process via MPI_Spawn. 

The program crashed on MPI_Intercomm_merge with the log 



------------------------------------------------------- 

.\src\logging\src\clog_commset.c:CLOG_CommSet_get_IDs() - 

PMPI_Comm_get_attr() fails! 

Backtrace of the callstack at rank 0: 

unable to read the cmd header on the pmi context, Error = -1 



I really appreciate any help 



Bruno 









_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you. 
_______________________________________________
discuss mailing list     discuss at mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: master.cpp
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20130605/3cb712cf/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: slave.cpp
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20130605/3cb712cf/attachment-0001.ksh>


More information about the discuss mailing list