Re: GDB (not) handling SIGINT...?

[Paul Smith <paul@mad-scientist.net>]

On Thu, 2018-11-15 at 13:55 +0000, Pedro Alves wrote:
> #2 - If you attach to a process instead of running it from GDB, then ctrl-c
>      reaches gdb first, and then GDB sends/forwards a SIGINT to the child process.

To me this seems to be the problem.  I've explicitly said I don't want
the signal passed to the process under debug (not a child process in
this situation right?)--in fact that's the default setting for SIGINT
--but yet GDB is still passing the signal along.

Isn't that incorrect behavior?

Is it there just for parity between the behavior of attaching to an
existing process versus running the process under GDB?  I'd prefer it
work one way and not the other, rather than not work either way :).

In my environment I'm _always_ attaching because our processes need to
be started through a separate service, or they don't have proper
security tokens to join the system.  So it would work OK for me if just
the attached version behaved as expected.  I get that others may have
different needs.