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.

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

Internal bug calling get_staged in debugger session #567

Closed
KlausC opened this issue Feb 23, 2023 · 2 comments
Closed

Internal bug calling get_staged in debugger session #567

KlausC opened this issue Feb 23, 2023 · 2 comments

Comments

@KlausC
Copy link

KlausC commented Feb 23, 2023

Just got this error, when in a Debugger session, after entering n:
This was originally posted as #48767

 445      if nrowB != ncol
>446          throw(DimensionMismatch("A is $(ncol) columns and B has $(nrowB) rows"))
 447      end
 448      _lmul!(A, B)
 449  end

About to run: (string)("A is ", 20000, " columns and B has ", 100, " rows")
1|debug> 
ERROR: MethodError: no method matching get_staged(::Core.MethodInstance)

Closest candidates are:
  get_staged(::Core.MethodInstance, ::UInt64)
   @ Core compiler/utilities.jl:117

Stacktrace:
 [1] kwcall(::NamedTuple{(:sizehint,), Tuple{Int64}}, ::Type{IOBuffer})
   @ Base iobuffer.jl:106
 [2] print_to_string(xs::Tuple{String, Int64, String, Int64, String})
   @ Base strings/io.jl:146
 [3] string(xs::Tuple{String, Int64, String, Int64, String})
   @ Base strings/io.jl:189
 [4] lmul!(A::UpperTriangular{Float64, SparseMatrixCSC{Float64, Int64}}, B::Matrix{Float64})
   @ SparseArrays ~/dev/juliadev/usr/share/julia/stdlib/v1.10/SparseArrays/src/linalg.jl:446
 [5] *(A::UpperTriangular{Float64, SparseMatrixCSC{Float64, Int64}}, B::Matrix{Float64})
   @ LinearAlgebra ~/dev/juliadev/usr/share/julia/stdlib/v1.10/LinearAlgebra/src/triangular.jl:1417

julia>
@maleadt
Copy link

maleadt commented Feb 24, 2023

You're probably using a nightly build before JuliaLang/julia#48763, so use a newer version.

@KlausC
Copy link
Author

KlausC commented Feb 24, 2023

You are right. I will close this issue.

@KlausC KlausC closed this as completed Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants