-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thread 1 "gcclassic" received signal SIGSEGV, Segmentation fault. #2502
Comments
Thanks for writing @YueZhang720. I wonder if this is something specific to the gcc 14.2.0 compilers. I can try to replicate that but I will first need to build libraries with spack for 14.2.0 so it may take me a while to get to this. There are a couple of errors like this: pomega=<error reading variable: value requires 1038528 bytes, which is more than max-value-size>,
fz=<error reading variable: value requires 129816 bytes, which is more than max-value-size>, so it may also be an issue on your cluster. If you have an older version of the GCC compilers (like 12.2.0) available, try that and see if you get the same error. |
Also which version of gdb are you using? You can type |
I have tried gcc 12.2.0, but it still has a segmentation fault with more errors. Is there anything wrong with my software or environment setting?
|
Thanks @YueZhang720. This is an out-of-bounds error in Cloud-J: At line 507 of file /public/home/jingzhoujiang/gcruns/CodeDir/src/Cloud-J/src/Core/cldj_fjx_sub_mod.F90
Fortran runtime error: Index '2146697216' of dimension 1 of array 'ooj' above upper bound of 48 @lizziel: Didn't we see a similar issue in Cloud-J before? |
Your name
Yue Zhang
Your affiliation
HKUST(GZ)
What happened? What did you expect to happen?
I'm running a full chemistry simulation from 2019/7/01-2019/08/01. My log file contains the following errors:
What are the steps to reproduce the bug?
Then I try to use gdb to backtrace the error:
What should I do next?
Please attach any relevant configuration and log files.
GC.log
gcfiles.zip
What GEOS-Chem version were you using?
14.4.3
What environment were you running GEOS-Chem on?
Local cluster
What compiler and version were you using?
gcc 14.2.0
Will you be addressing this bug yourself?
Yes, but I will need some help
In what configuration were you running GEOS-Chem?
GCClassic
What simulation were you running?
Full chemistry
As what resolution were you running GEOS-Chem?
2x2.5
What meterology fields did you use?
MERRA-2
Additional information
No response
The text was updated successfully, but these errors were encountered: