I am profiling the python with Vmprof. Everything is OK if without Numba. However, a message of "Process finished with exit code 132 (interrupted by signal 4: SIGILL)" would be showed when I try to profile the codes with Numba.
Is it possible to ignore such signal and continue to profile?
I am profiling the python with Vmprof. Everything is OK if without Numba. However, a message of "Process finished with exit code 132 (interrupted by signal 4: SIGILL)" would be showed when I try to profile the codes with Numba.
Is it possible to ignore such signal and continue to profile?
Thanks a lot in advance.
Feng Wang @ SKAO