Fortran error code when Ctrl+C is pressed

[LynBar]

Bug Description

If I import the QuantumToolbox package and run any code, pressing Crtl+C now no longer just throws an interrupt exception, it kills the instance of Julia that is running and gives a Fortran error code .
"forrtl: error (200): program aborting due to control-C event
Initialization of symbol handler failed. Error code %d:87"
This only seems to happen when the QuantumToolbox package is imported so I'm really not sure what's happening.

Code to Reproduce the Bug

using QuantumToolbox
while true
end

Code Output

forrtl: error (200): program aborting due to control-C event
Initialization of symbol handler failed. Error code %d:87

Expected Behaviour

I expect the running programme to be killed when I press Ctrl+C, not the Julia instance.

Your Environment

QuantumToolbox.jl: Quantum Toolbox in Julia
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Copyright © QuTiP team 2022 and later.
Current admin team:
    Alberto Mercurio and Yi-Te Huang

Package information:
====================================
Julia              Ver. 1.11.6
QuantumToolbox     Ver. 0.34.0
SciMLOperators     Ver. 1.5.0
LinearSolve        Ver. 3.36.0
OrdinaryDiffEqCore Ver. 1.30.0

System information:
====================================
OS       : Windows (x86_64-w64-mingw32)
CPU      : 14 × Intel(R) Core(TM) Ultra 5 125U
Memory   : 31.458 GB
WORD_SIZE: 64
LIBM     : libopenlibm
LLVM     : libLLVM-16.0.6 (ORCJIT, alderlake)
BLAS     : libopenblas64_.dll (ilp64)
Threads  : 1 (on 14 virtual cores)

Additional Context

Status \\10.204.28.1\Docs5\barry.lynch\linuxhome\Documents\JuliaCode\IRC_Code\Testing\Project.toml [6c2fb7c5] QuantumToolbox v0.34.0
If I call ccall(:raise, Cvoid, (Cint,), Base.SIGINT) this still acts as normal, and keeps the julia instance running, so something seems to be overriding the key shortcut.

I assume this is being caused by some package imported by QuantumToolbox, but have no idea where to start looking so any help with this would be much appreciated!

[ytdHuang]

I don't think this is an issue related to our package or even julia programming language.

If you search for this error message in internet, it also happends in Python when you are using a Windows OS.

[LynBar]

I did see a lot of the Python related problems, however this specifically only occurs when I import the QuantumToolbox package.
If its not imported the interrupt works fine.
I think the problem is on my side, but I cant figure out what's going wrong. I tried previous versions of Julia and the package where everything worked perfectly before, but I still get the bug.
Maybe I'll just try reinstalling Julia if this problem only exists for me.

[LynBar]

I fixed it by adding ENV["FOR_DISABLE_CONSOLE_CTRL_HANDLER"] = "1" to my startup.jl file.
This just stops the Intel Fortran runtime from installing its own interrupt handler.
I tried to find the package that imports a Fortran dependency, but couldn't find anything so I'm just going to leave it at this.

[albertomercurio]

One package that may import fortran is LinearAlgebra.jl itself.

[LynBar]

I did try to check that with BLAS.get_config() but I seem to be using OpenBLAS which shouldn't cause any fortran runtime stuff (at least I think).
Does QuantumToolbox change any of the default LinearAlgebra.jl settings?
I didn't try all to hard to diagnose the issue, just checked if there were any fortran dependency stuff with Libdl.dllist() and couldn't see anything obvious.

[LynBar]

After a bit of investigation I've found that the LinearSolve.jl module causes the issue. It imports MKL.jl which builds binaries with the Intel FORTRAN runtime libiomp5. This then overwrites my Interrupts.

[albertomercurio]

I see, maybe you can open an issue at LinearSolve.jl.