-
Notifications
You must be signed in to change notification settings - Fork 121
Fix seg fault when fd_order is on #704
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
Conversation
buff_size changed for idwbuff but not updated for startx, starty, and startz.
Assign finite difference number and keep the halo region the same.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #704 +/- ##
=========================================
Coverage ? 43.04%
=========================================
Files ? 61
Lines ? 16061
Branches ? 1798
=========================================
Hits ? 6914
Misses ? 8157
Partials ? 990 ☔ View full report in Codecov by Sentry. |
|
I'm not sure. Something about this is still confusing to me. Maybe it's clearer to @henryleberre since he just edited all of these. |
|
I think I understand better now after looking at this more properly. |
Description
The buffer_size is not initialized for all the variable bound constant (e.g.
idwbuff(2)%beg:idwbuff(2)%endfrom PR# 653) when fd_order is on. This will cause seg fault issue on variables likeflux_gsrc_n. Maybe @henryleberre can confirm this.Type of change
Please delete options that are not relevant.
Scope
If you cannot check the above box, please split your PR into multiple PRs that each have a common goal.
How Has This Been Tested?
Turn on
fd_orderand the seg fault issue is resolved.Test Configuration:
Checklist
If your code changes any code source files (anything in
src/simulation)To make sure the code is performing as expected on GPU devices, I have: