You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m running ADFlow with adjoint solver in docker (image: u20-gcc-ompi-latest) on WIN10 system. I can run with a small grid number. When the grid number is more than 2.0e5, the adjoint solver encounters a “Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range” error.
My computer memory is 100G, and I run with 8 CPU cores.
How can I solve this problem? Thanks.
[1]PETSC ERROR: ------------------------------------------------------------------------
[1]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[1]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[1]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind
[1]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[1]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run
[1]PETSC ERROR: to get more information on the crash.
[1]PETSC ERROR: --------------------- Error Message --------------------------------------------------------------
[1]PETSC ERROR: Signal received
[1]PETSC ERROR: See https://petsc.org/release/faq/ for trouble shooting.
[1]PETSC ERROR: Petsc Release Version 3.15.5, Sep 29, 2021
[1]PETSC ERROR: Unknown Name on a real-opt-gcc-3.15.5 named db34c9153157 by Unknown Sat Aug 27 00:43:27 2022
[1]PETSC ERROR: Configure options --with-shared-libraries --download-superlu_dist --download-parmetis=yes --download-metis=yes --with-fortran-interfaces=1 --with-debugging=no --with-cxx-dialect=C++11 --with-cc=mpicc --with-cxx=mpicxx --with-fc=mpifort --COPTFLAGS=-O2 --CXXOPTFLAGS=-O2 --FOPTFLAGS=-O2 --download-fblaslapack --PETSC_ARCH=real-opt-gcc-3.15.5 --with-scalar-type=real
[1]PETSC ERROR: #1 User provided function() at unknown file:0
[1]PETSC ERROR: Run with -malloc_debug to check if memory corruption is causing the crash.
The text was updated successfully, but these errors were encountered:
I’m running ADFlow with adjoint solver in docker (image: u20-gcc-ompi-latest) on WIN10 system. I can run with a small grid number. When the grid number is more than 2.0e5, the adjoint solver encounters a “Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range” error.
My computer memory is 100G, and I run with 8 CPU cores.
How can I solve this problem? Thanks.
[1]PETSC ERROR: ------------------------------------------------------------------------
[1]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[1]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[1]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind
[1]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[1]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run
[1]PETSC ERROR: to get more information on the crash.
[1]PETSC ERROR: --------------------- Error Message --------------------------------------------------------------
[1]PETSC ERROR: Signal received
[1]PETSC ERROR: See https://petsc.org/release/faq/ for trouble shooting.
[1]PETSC ERROR: Petsc Release Version 3.15.5, Sep 29, 2021
[1]PETSC ERROR: Unknown Name on a real-opt-gcc-3.15.5 named db34c9153157 by Unknown Sat Aug 27 00:43:27 2022
[1]PETSC ERROR: Configure options --with-shared-libraries --download-superlu_dist --download-parmetis=yes --download-metis=yes --with-fortran-interfaces=1 --with-debugging=no --with-cxx-dialect=C++11 --with-cc=mpicc --with-cxx=mpicxx --with-fc=mpifort --COPTFLAGS=-O2 --CXXOPTFLAGS=-O2 --FOPTFLAGS=-O2 --download-fblaslapack --PETSC_ARCH=real-opt-gcc-3.15.5 --with-scalar-type=real
[1]PETSC ERROR: #1 User provided function() at unknown file:0
[1]PETSC ERROR: Run with -malloc_debug to check if memory corruption is causing the crash.
The text was updated successfully, but these errors were encountered: