Reset N_MAX to 0 in DESTROY_PLANS_FFTW #119
Merged
+1
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #118. In the test in question DESTROY_PLANS_FFTW is called twice; the first time is fine and the deallocations are done, but the second time is not okay because when the loop iterates there is an attempt to dereference TW%FFTW_PLANS when it is deallocated. The fix sets N_MAX to 0 so that the loop doesn't execute.
What do you think?