SIGSEGV signal (forbidden memory area access) intercepted!

Questions and remarks about code_saturne usage
Forum rules
Please read the forum usage recommendations before posting.
Post Reply
andrea28
Posts: 41
Joined: Fri Apr 15, 2016 7:25 pm

SIGSEGV signal (forbidden memory area access) intercepted!

Post by andrea28 »

Hi,
When I stop a calculation or when is at its last step, I am getting this error:
SIGSEGV signal (forbidden memory area access) intercepted!
Call stack:
1: 0x7f7df9ea3d67 <ple_locator_exchange_point_var+0x277> (libple.so.1)
2: 0x7f7dfa174f50 <cs_boundary_conditions_mapped_set+0x190> (libsaturne.so.0)
3: 0x7f7dfa175e8b <cs_f_boundary_conditions_mapped_set+0x1fb> (libsaturne.so.0)
4: 0x401f51 <cs_user_boundary_conditions_+0x751> (cs_solver)
5: 0x7f7dfa25ad20 <tridim_+0x3640> (libsaturne.so.0)
6: 0x7f7dfa1391c6 <caltri_+0x3006> (libsaturne.so.0)
7: 0x7f7dfa10fe2e <cs_run+0x3fe> (libsaturne.so.0)
8: 0x7f7dfa10f922 <main+0x112> (libsaturne.so.0)
9: 0x7f7df7895b15 <__libc_start_main+0xf5> (libc.so.6)
10: 0x401739 <> (cs_solver)
End of stack

The problem is related to the mapped-inlet routine, since without it everything works.
Do you have any hint?

Thanks,

Andrea
Attachments
cs_user_boundary_conditions-mapped_inlet.f90
(10.87 KiB) Downloaded 199 times
Yvan Fournier
Posts: 4079
Joined: Mon Feb 20, 2012 3:25 pm

Re: SIGSEGV signal (forbidden memory area access) intercepte

Post by Yvan Fournier »

Hello,

Is your case small enough to post ? I see no obvious problem, so I would need to run the case to reproduce the issue.

Regards,

Yvan
Post Reply