Random Segmentation faults
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- fortran
- Domain
- hpc
Research direction
Start with the supplied PARAM.in and the GSL backtrace, focusing on the call into gsl_spline_init. Reproduce the simulation if possible and use the reported stack to locate the project-side caller; done means identifying and correcting the cause of the intermittent segmentation fault and confirming the supplied simulation completes reliably.
Written by the indexing model from the issue text.
Description
Hi,
I am running RAM-SCB for several days (simulation time) and it sometimes randomly crashes with a segfault. I have found that rerunning the simulation several times until it can finally end is my best solution for right now. I unfortunately cannot make a minimal reproducible example. This was compiled using GSL v2.7. Below is the segfault message and PARAM.in file:
stderr:
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x2b713ce7862f in ???
#1 0x2b713ba49cd8 in gsl_spline_init
at ../../interpolation/spline.c:72
#2 0x5e87db in ???
#3 0x4991c8 in ???
#4 0x4ed8d3 in ???
#5 0x4b950b in ???
#6 0x4918f7 in ???
#7 0x404cb4 in ???
#8 0x404ab6 in ???
#9 0x2b713d0a7554 in ???
#10 0x404ae6 in ???
#11 0xffffffffffffffff in ???
PARAM.in:
PARAM File for Test Week 05 Simulation
Derived from PARAM.in.default
#DESCRIPTION
Test_Week05: 2005-05-12
#EVENT
test_week05_final
************** REQUIRED BLOCK *****************
#STARTTIME
2005 iYear
5 iMonth
12 iDay
00 iHour
00 iMinute
0 iSecond
0.0 FracSecond
#STOPTIME
2005 iYear
5 iMonth
18 iDay
23 iHour
59 iMinute
59 iSecond
0.0 FracSecond
***********************************************
*************** TIMING BLOCK ******************
#MAXTIMESTEP
20.0 MaxHalfStep
#MINTIMESTEP
0.01 MinHalfStep
#VARIABLEDT
T DoVarDt
#COMPONENT_TIMESTEPS
300.0 SCBTimeStep
300.0 BCTimeStep
300.0 EFTimeStep
***********************************************
*************** COMPONENT BLOCK ***************
#OUTERBOUNDARY
LANL NameBoundPlasma
T89D NameBoundMag
MAXW NameDistribution
#EFIELD
WESC NameEfield
F UseEfInd
***********************************************
***************** RAM BLOCK *******************
***********************************************
***************** SCB BLOCK *******************
#SCBFLAGS
F Isotropic
F ReduceAnisotropy
T BetaExtrapolation
F AzimuthalOffset
F EmptyLossCone
T AdaptiveMesh
#SCBSMOOTHING
1 PressureSmoothing
3 SavitzyGolayIterations
***********************************************
***************** INPUT BLOCK *****************
#OMNIFILE
omni.txt NameOmniFile
#OMNIFILESOURCE
T UseSWMFFormat
#INDICES_FILE
RamIndices.txt NameIndicesFile
***********************************************
***************** OUTPUT BLOCK ****************
#SAVERESTART
3600.0 DtSaveRestart
T DoSaveFinalRestart
#TIMEDRESTART
F TimedRestartFiles
#LOGFILE
600.0 DtLogFileWrite
#SAVEFLUX
600.0 DoSaveFlux
#OUTPUT_FREQUENCY
-1 DtPressureFileWrite
-1 DthIFileWrite
-1 DtEFieldFileWrite
-1 DtMAGxyzFileWrite
#DUMP3DFLUX
F DoDump3DFlux
***********************************************
Thank you for your time.
- Dominant language
- Fortran
- Stars
- 16
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lanl/RAM-SCB
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
flux-framework/flux-coral2#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
kynema/kynema-sgf#2064 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
EMsoft-org/EMsoftOO#20 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100