-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime failure of tutorial example 03 copy on amd-epyc #572
Comments
What are the runtime errors? |
Martin's description of the problem is good. I will reiterate in my own words, the goal is to build a single file tutorial 3 (which is the first tutorial that accesses a mesh) with a CMake/Make tool chain rather than the flecsi-tutorial/flecsit tool chain. One can only presume the issue is configuration. What makes this hard is we are getting run time, not build time errors. Martin's standalone app generates the following runtime error: terminate called after throwing an instance of 'std::runtime_error' [cn4002:08266] *** Process received signal *** My original standalone app generates the following runtime error: terminate called after throwing an instance of 'std::runtime_error' [cn4002:08248] *** Process received signal *** |
I'll note also that the error ending with "Make sure it has been properly registered!" might appear to have been caused by a simple misuse of the register/get-handle/execute pattern via FleCSI's macros, but I don't believe that it is. The code uses those correctly, just as index-spaces.cc (tutorial example 03) does over the course of the last couple dozen lines in its source. |
please provide source |
|
That's just Tutorial 03 with specialization material integrated directly into one source file. |
source file: slinky-marty.cc (put in /src directory at same level as CMakeLists.txt):
current CMakeLists.txt:
invocation from /build:
in my case: |
I dont see a "flecsi_register_data_client" as the errror suggests |
It looks like one missing link (good eye, @charest) is that we're missing:
as from flecsi-tutorial/specialization/mesh.cc. The failure to have this shows up as neither a compile-time nor a link-time error. The script flecsi/build/CMakeFiles/flecsi-tutorial-install.sh sets:
which would have given us the inline bool (and resulting registration) inserted by the flecsi_register_data_client(mesh_t, clients, mesh) macro, via the linked library. This explains why flecsit ended up with what it needed, but the more-direct build was missing something. @Shevits if you insert:
then it gets us past the registration error. Now I'm still getting:
on my own machine, but it's progress. |
where are your spmd and tlt init functions? This example is not complete. |
The invalid index space error is what we were originally getting... |
Probably close to a resolution. Danny and I will meet on Monday. |
Made good progress at this morning's meeting. Participants were Danny, Evgeny, Irina, Martin, and Navamita. |
Danny Shevitz copied flecsi-tutorial example 03 to an external (to flecsi-tutorial) location, in preparation for integrating some of its contents into a separate application to be built in cmake/make fashion rather than with flecsit. The code has been failing with cryptic runtime errors, even while the same code as built with flecsit runs as intended.
We have explored various leads including, but not limited to: (1) Ensuring the same underlying compiler and flags in the cmake/make system as compared with flecsit. (2) Looking into debug- vs. release-mode issues. (3) Guaranteeing that paths were such that we pulled in the same specialization in both cases, instead of inadvertently picking up a different and incompatible one in the problem case. (4) Issues related to modules and libraries.
We also hand-#included all relevant specialization/ material into the main code, to make a single self-contained file that replicates the original tutorial example. FleCSI Static Analyzer reports no known problems, the same as it does with the original tutorial code.
So far, no luck in tracking down the error. We'll continue exploring, and report on what proves to be the problem.
The text was updated successfully, but these errors were encountered: