-
Notifications
You must be signed in to change notification settings - Fork 94
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
Crash in dpivotL() due to uninitialized variable #33
Comments
Hi Xiaoye Sherry Li, I am facing the same issue mentioned by @coronasky for a singular sparse matrix. The program crashes at the below line:
As described by @coronasky , this seems to be an issue with the uninitialized variable "pivrow" Can you please look into this problem and share your comments? I would also like to know the motivation of using "#if 1" condition since the code inside #else will never run. Similar to the observation of @coronasky , there is no crash if I edit it to "#if 0". Can we keep it as "#if 0" and what are the implications of doing so? Regards, |
The old "#else" branch is not correct if there are several "numerical zeros" in the current column. Seems like your matrix is structurally zero in that column, and the column is not represented in the meta data structure? At the crash point, can you print out the following variables: fsupc, nsupc, nsupr, pivptr, lsub_ptr[pivptr], |
fix compile errors with 64bit-indices build
Merge branch 'master' of https://github.com/xiaoyeli/superlu_dist
Hi Xiaoye,
When using superLU, I found a crash in dpivotL() caused by possible uninitialized variable.
The issue happens when the sparse matrix is singular, with a few all-zero rows/columns.
Where is the stacktrace:
Because of the all-zero rows, Glu->lsub[] 's elements are not initialized. I believe they would be properly set in dsnode_dfs() if the rows/columns are non-zero.
Due to this problem, the function crashed at line 138:
I have no idea what's behind the "#if 1" condition. Maybe there are other considerations for the singularity?
But if I change it to "#if 0", then the crash is gone.
Would you please take a look at this problem? Probably the same issue exists in single and complex versions.
Regards,
Haotian
The text was updated successfully, but these errors were encountered: