https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94394
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> --- (In reply to ammy.yi from comment #3) > Actually, there is some random kernel panic here. > > The following steps may reproduce this issue: > > 1. Enable gcov in kconfig > 2. build kernel and boot to system > 3. Do following load/unload modules steps > > modprobe stm_p_basic > modprobe intel_th_pci > modprobe intel_th_sth > modprobe intel_th_msu > modprobe stm_console > > modprobe -r stm_p_basic > modprobe -r intel_th_pci > modprobe -r intel_th_sth > modprobe -r intel_th_msu > modprobe -r stm_console Would it be possible to provide a stack-traces where it usually causes a kernel panic? > > Hi martin, > > If it is libgcov issue, do you know where to file issue for it? I would create a normal linux kernel bug. The pseudo-runtime is implemented in kernel/gcov subfolder.
