Page 1 of 1

Help! Error executing calculation.

Posted: Wed May 25, 2022 9:07 am
by danwell
Hello colleagues, I hope you can help me with a problem that I have been dragging for a few days.

I have added a new variable for my study, it works perfectly, in the listing file it reads and executes all the added variables, but where I have a problem is in the post processing, when it is going to write in RESU and it throws me the following error:

Code: Select all

Error executing calculation.

See the Code_Saturne log (listing) and error* files for more information.


 ****************************
  Post-calculation operations
 ****************************

 Error in calculation stage.

I understand that it is due to a memory overflow but I can't find a solution.

Detail more information:

Code: Select all

 End writing info on calculation

SIGSEGV signal (forbidden memory area access) intercepted!

Call stack:
   1: 0x7fa5004600c0 <+0x430c0> (libc.so.6)
   2: 0x7fa5004cec0a <+0xb1c0a> (libc.so.6)
   3: 0x7fa500492d5c <+0x75d5c> (libc.so.6)
   4: 0x7fa500493dfd <+0x76dfd> (libc.so.6)
   5: 0x7fa5004a8fca <+0x8bfca> (libc.so.6)
   6: 0x7fa50047ee26 <__snprintf+0x96> (libc.so.6)
   7: 0x557255810588 <+0x18588> (cs_solver)
   8: 0x557255812487 <cs_lagr_restart_write_particle_data+0x6b1> (cs_solver)
   9: 0x5572558022e5 <cs_restart_lagrangian_checkpoint_write+0x31c> (cs_solver)
  10: 0x5572557ffb26 <lagout_+0xd> (cs_solver)
  11: 0x7fa500ae3f16 <caltri_+0x4a22> (libsaturne-6.0.so)
  12: 0x7fa5029cb957 <cs_run+0x53e> (libcs_solver-6.0.so)
  13: 0x7fa5029cbc97 <main+0x19f> (libcs_solver-6.0.so)
  14: 0x7fa5004410b3 <__libc_start_main+0xf3> (libc.so.6)
  15: 0x5572557ffa4e <_start+0x2e> (cs_solver)
end-of-stack

Thank you very much in advance.
I am a simple newbie who is learning. If you need anything else let me know. All I'm looking for is to finally fix this.

(Saturn Code V6.0.2)

Re: Help! Error executing calculation.

Posted: Wed May 25, 2022 9:29 am
by Yvan Fournier
Hello,

The crash seems to be when writing the Lagrangian restart files, but could come from an earlier memory access (overwrite) issue.

Could you test if you have the same problem with version 7.0 ? And a small test case allowing reproduction of the issue would help (preferably for v7.0; v6.0 will be maintained until June 2023 for continuation of studies started before v7.0 was released, but for any new case, v7 is recommended).

If your test case is large, at least the XML and user-defined source files would be helpful.

Best regards,

Yvan