Hi all,
I am trying to run code_saturne 7.0.2 with ssh-aerosol model, but I always got the error like this:
Hydrostatic pressure computation:
updating the Dirichlets at the end (CALHYD)
SIGSEGV signal (forbidden memory area access) intercepted!
Call stack:
1: 0x70d38425d704 <cs_turbulence_ke+0xac4> (libsaturne-7.0.so)
2: 0x5fe53923e275 <tridim_+0x4371> (cs_solver)
3: 0x70d383cbee90 <caltri_+0x1c8f> (libsaturne-7.0.so)
4: 0x70d384c88ba1 <main+0x721> (libcs_solver-7.0.so)
5: 0x70d38342a1ca <+0x2a1ca> (libc.so.6)
6: 0x70d38342a28b <__libc_start_main+0x8b> (libc.so.6)
7: 0x5fe539205625 <_start+0x25> (cs_solver)
End of stack
Really thanks if you have any suggestion for this
SIGSEGV signal issue
Forum rules
Please read the forum usage recommendations before posting.
Please read the forum usage recommendations before posting.
SIGSEGV signal issue
- Attachments
-
- run_solver.log
- (144.13 KiB) Downloaded 123 times
-
- Posts: 4226
- Joined: Mon Feb 20, 2012 3:25 pm
Re: SIGSEGV signal issue
Hello,
It is not possible to determine whether this is due to an issue in the code or in you user-defined functions, so you need to:
- ideally, run this under under a debugger on your side, to get more details
- otherwise, post you user-defined files.
Also, v7.0.2 is not up to date, so you should upgrade to v7.0.6 (or the head of the v7 git branch), in case this might be due to an already corrected bug.
Better, you should update to v8.0, or v9.0 (not yet released, but will be released this month, and validation is nearly finished, so the v9.0 branch on GitHub is already quite stable).
Best regards,
Yvan
It is not possible to determine whether this is due to an issue in the code or in you user-defined functions, so you need to:
- ideally, run this under under a debugger on your side, to get more details
- otherwise, post you user-defined files.
Also, v7.0.2 is not up to date, so you should upgrade to v7.0.6 (or the head of the v7 git branch), in case this might be due to an already corrected bug.
Better, you should update to v8.0, or v9.0 (not yet released, but will be released this month, and validation is nearly finished, so the v9.0 branch on GitHub is already quite stable).
Best regards,
Yvan