JuliaDebug / JuliaDebug/Cthulhu.jl
VSCode-only ERROR: unhandled `Compiler.CallInfo` of type Compiler.VirtualMethodMatchInfo"
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 709
- Forks
- 46
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 2
Description
It's totally fine outside of VSCode, on the Windows Terminal. FWIW @code_warntype says both * and mul! (generated function) are type stable, so not sure why there's a virtual method involved. This is on 1.12.5.
On FFTA.jl's main branch:
julia> using FFTA, Cthulhu
julia> x = rand(ComplexF64, 8, 8); p = plan_fft(x, 1:2);
julia> @descend p * x
*(p::FFTA.FFTAPlan_cx{T, N1}, x::AbstractArray{T, N2}) where {T<:Complex, N1, N2} @ FFTA Q:\FFTA.jl\src\plan.jl:279
ERROR: unhandled `Compiler.CallInfo` of type Compiler.VirtualMethodMatchInfo; you may inspect `Main.provider|result|info|argtypes|rt`
Stacktrace:
[1] error(s::String)
@ Base .\error.jl:44
[2] process_info(provider::Cthulhu.DefaultProvider, result::Cthulhu.LookupResult, info::Compiler.CallInfo, argtypes::Vector{…}, rt::Any, exct::Any, effects::Nothing)
@ Cthulhu Q:\.julia\packages\Cthulhu\7jFQA\src\compiler\reflection.jl:253
[3] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\compiler\reflection.jl:62
[4] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\compiler\reflection.jl:19
[5] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\compiler\codeview.jl:257
[6] top-level scope (repeats 16 times)
@ Q:\.julia\packages\Cthulhu\7jFQA\src\compiler\codeview.jl:271
[7] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\compiler\codeview.jl:255
[8] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\compiler\codeview.jl:133
[9] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\compiler\codeview.jl:93
[10] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\descend.jl:88
[11] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\ui.jl:102
[12] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\descend.jl:87
[13] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\descend.jl:18
[14] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\descend.jl:14
[15] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\descend.jl:24
[16] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\descend.jl:21
[17] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\descend.jl:28
[18] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\descend.jl:27
[19] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\descend.jl:31
[20] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\descend.jl:31
[21] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\descend.jl:4
[22] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\descend.jl:1
[23] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\Cthulhu.jl:174
[24] top-level scope
@ Q:\.julia\packages\Cthulhu\7jFQA\src\Cthulhu.jl:173
[25] top-level scope
@ REPL[3]:1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the @descend p * x example from the issue in VSCode and Windows Terminal. Start at src/compiler/reflection.jl:253 and follow the @descend entry points shown in the stack trace, especially src/descend.jl and src/compiler/codeview.jl. Done means the reported Compiler.VirtualMethodMatchInfo error is handled without breaking the existing descent workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia, vscode
- Domain
- compilers, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100