charm AT lists.siebelschool.illinois.edu
Subject: Charm++ parallel programming system
List archive
- From: "Galvez Garcia, Juan Jose" <jjgalvez AT illinois.edu>
- To: Jozsef Bakosi <jbakosi AT lanl.gov>, "charm AT cs.illinois.edu" <charm AT cs.illinois.edu>
- Subject: RE: [charm] late entry method registration
- Date: Fri, 7 Sep 2018 16:00:13 +0000
- Accept-language: en-US
- Authentication-results: illinois.edu; spf=pass smtp.mailfrom=jjgalvez AT illinois.edu; dmarc=pass header.from=illinois.edu
Jozsef,
Sorry for the late response.
This error happens when entry methods are registered after Charm++ has been initialized. Normally this would mean that a chare type is being registered after the runtime has initialized. On a regular Charm++ application this should never happen, but maybe you are using some non-standard initialization pattern. Can you give more details on how initialization works in your use case, and if you are doing Charm++ / MPI interop, or maybe dynamically linking charm modules?
-Juan
From: Jozsef Bakosi
Sent: Friday, August 31, 2018 2:50 PM
To: charm AT cs.illinois.edu
Subject: [charm] late entry method registration
I'm getting:
Charm++: late entry method registration happened after init
Entry point: MPIRunner(), addr: 0x7ffff7dd6800
------------- Processor 0 Exiting: Called CmiAbort ------------
Reason: Did you forget to instantiate a templated entry method in a .ci file?
MPIRunner is a nodegroup, but not even templated. What can be wrong?
Thanks,
Jozsef
- RE: [charm] late entry method registration, Galvez Garcia, Juan Jose, 09/07/2018
- Re: [charm] late entry method registration, Jozsef Bakosi, 09/17/2018
Archive powered by MHonArc 2.6.19.