This is a GDB bug that happens rarely, you might want to try tracing an address that's visited frequently (poll, syscalls etc) to increase your chances of triggering this bug. After the trace session ends, GDB won't be able to stop the process with interrupt command
However, this can be fixed easily by running a second trace session. The reason for this behavior will be investigated
This is a GDB bug that happens rarely, you might want to try tracing an address that's visited frequently (poll, syscalls etc) to increase your chances of triggering this bug. After the trace session ends, GDB won't be able to stop the process with
interruptcommandHowever, this can be fixed easily by running a second trace session. The reason for this behavior will be investigated