Search found 26 matches
- Sun Oct 13, 2019 4:33 pm
- Forum: code_saturne usage
- Topic: SIGSEGV signal writing results in extra operations
- Replies: 7
- Views: 4279
Re: SIGSEGV signal writing results in extra operations
Hello Yvan, I'm running on an ubuntu 19.04 VM. The fortran compiler is f95 and the c compiler is cc. Martin Ferrand told me that user_extra_operations_initialize() is called by inivar.f90 indeed. He advised me to make a copy of the file, insert a bit of print code and recompile with --enable-debug i...
- Wed Oct 09, 2019 4:48 pm
- Forum: code_saturne usage
- Topic: SIGSEGV signal writing results in extra operations
- Replies: 7
- Views: 4279
Re: SIGSEGV signal writing results in extra operations
To be even more specific, with the help of a much more CS qualified person, I came to the point where cs_user_extra_operations() and cs_user_extra_operations_initialize() don't seem to be called during calculation. That would explain the segmentation fault because, the file was simply never created ...
- Wed Oct 09, 2019 12:27 pm
- Forum: code_saturne usage
- Topic: SIGSEGV signal writing results in extra operations
- Replies: 7
- Views: 4279
Re: SIGSEGV signal writing results in extra operations
Ok I found the problem, but can't seem to solve it... It's related to extra operations done after calculation is finished in cs_user_extra_operations.c The segmentation fault comes from the fclose() function that seems to consider the pointer to the file is NULL. What am I doing wrong ? Here is my c...
- Wed Oct 09, 2019 1:11 am
- Forum: code_saturne usage
- Topic: SIGSEGV signal writing results in extra operations
- Replies: 7
- Views: 4279
SIGSEGV signal writing results in extra operations
Hi there, After a successfull instalaltion of Code_saturne 6.0 a few weeks ago, I went at it again, downloaded the last version (September 26th) but on the first run of a previously working case, i had the following error : SIGSEGV signal (forbidden memory area access) intercepted! Call stack: 1: 0x...
- Wed Sep 18, 2019 11:26 am
- Forum: Installation issues
- Topic: Compilation error code_saturne 6.0 beta - "no member named 'coeff_send' "
- Replies: 2
- Views: 2758
Re: Compilation error code_saturne 6.0 beta - "no member named 'coeff_send' "
Hello,
It worked perfectly with the automated installer, many thanks !
SOLVED !
It worked perfectly with the automated installer, many thanks !
SOLVED !
- Tue Sep 17, 2019 1:51 pm
- Forum: Installation issues
- Topic: Compilation error code_saturne 6.0 beta - "no member named 'coeff_send' "
- Replies: 2
- Views: 2758
Compilation error code_saturne 6.0 beta - "no member named 'coeff_send' "
Hi there, When exectuing the "make" command for new 6.0-beta, I get the following errors : cs_equation_assemble.c:603:48: error: ‘cs_matrix_assembler_t’ {aka ‘const struct _cs_matrix_assembler_t’} has no member named ‘coeff_send_n_rows’ const cs_lnum_t e_r_id = _g_binary_search(ma->coeff_s...