Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Sparse matrix \ throws error and segfaults with symmetric RHS #9915

Closed
simonster opened this issue Jan 25, 2015 · 8 comments
Closed

Sparse matrix \ throws error and segfaults with symmetric RHS #9915

simonster opened this issue Jan 25, 2015 · 8 comments
Labels
domain:arrays:sparse Sparse arrays kind:bug Indicates an unexpected problem or unintended behavior

Comments

@simonster
Copy link
Member 

julia> speye(2)\speye(2)
CHOLMOD error: B cannot be stored in symmetric mode

signal (11): Segmentation fault
call at sparse/cholmod.jl:452
solve at sparse/cholmod.jl:825
\ at sparse/cholmod.jl:878
A_ldiv_B! at sparse/cholmod.jl:870
jl_apply_generic at /usr/local/julia/usr/bin/../lib/libjulia.so (unknown line)
\ at linalg/generic.jl:241
jl_apply_generic at /usr/local/julia/usr/bin/../lib/libjulia.so (unknown line)
unknown function (ip: 1224344712)
unknown function (ip: 1224342223)
unknown function (ip: 1224414669)
jl_toplevel_eval_in at /usr/local/julia/usr/bin/../lib/libjulia.so (unknown line)
eval_user_input at REPL.jl:54
jlcall_eval_user_input_223884 at  (unknown line)
jl_apply_generic at /usr/local/julia/usr/bin/../lib/libjulia.so (unknown line)
anonymous at task.jl:83
unknown function (ip: 1224370721)
unknown function (ip: 0)
fish: Job 1, “julia” terminated by signal SIGSEGV (Address boundary error)
@simonster simonster added kind:bug Indicates an unexpected problem or unintended behavior domain:arrays:sparse Sparse arrays labels Jan 25, 2015
@andreasnoack
Copy link
Member

I'm working on a quite extensive overhaul of cholmod.jl so I'll try to include a fix for this to avoid other changes to the file while I'm working on it.

@andreasnoack
Copy link
Member

Okay. I have found the bug and will fix it as part of the my overhaul.

@tkelman
Copy link
Contributor

tkelman commented Jan 25, 2015

@andreasnoack please separate the bugfix from major changes. This bug is present on release-0.3 as well, and should be fixed there if at all possible.

@andreasnoack
Copy link
Member

I'd like to avoid too many conflicts here, but the fix is so small that it shouldn't be an issue. I'll see if I can separate out the bug fix. For 0.3 it shouldn't be an issue as the other changes won't be back ported.

@tkelman
Copy link
Contributor

tkelman commented Jan 25, 2015

If the bug fix will be a separate commit that can be cleanly backported, that's perfect and it doesn't matter too much whether or not it's in the same PR. Thanks, just wanted you to keep it in mind so the bugfix won't have to be dissected piecemeal out of a bigger commit.

@andreasnoack
Copy link
Member

@JuliaBackports

@simonster
Copy link
Member Author

Thanks!

andreasnoack added a commit that referenced this issue Jan 28, 2015
@andreasnoack @tkelman
Fix #9915. When solving SparseMatrixCSC\SparseMatrixCSC and the rhs i…
6e32fc7 
…s symmetric,

the rhs shouldn't be stored with symmetric flag set.

(cherry picked from commit 1627a68)
@tkelman
Copy link
Contributor

tkelman commented Jan 28, 2015

backported in 6e32fc7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
domain:arrays:sparse Sparse arrays kind:bug Indicates an unexpected problem or unintended behavior
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@simonster @andreasnoack @tkelman