"finish" command leads to SIGTRAP

Pedro Alves palves@redhat.com
Thu Feb 21 13:12:00 GMT 2019

Might be unrelated, but ISTR that there used to be a kernel bug
that would lead to the cpu's trace flag getting stuck set
when you step in a signal handler.  That would result in
SIGTRAP happening at every step from that point on.  Could
that be the case here?

I'd look at "set debug displaced on" too.  Otherwise, it's a matter
at staring at the logs, and trying to understand what is happening.
Basically, "finish" sets a breakpoint at the caller and runs to it.
But all sorts of other things can happen behind the scenes.

Pedro Alves

More information about the Gdb mailing list