[Bug threads/28347] FAIL: gdb.threads/signal-sigtrap.exp: sigtrap thread 1: signal SIGTRAP reaches handler

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=28347

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |palves at sourceware dot org,
                   |                            |simark at simark dot ca

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
So, what I understand that happens is:
- gdb command "signal SIGTRAP" sends the signal to the main thread using
  PTRACE_CONT
- the signal is blocked, so it becomes pending
- when the signal is unblocked, the pending signal is delivered, but because
the
  inferior is ptraced, gdb is notified, and gdb does the stop/print/pass
  processing.

This seems to contradict the documentation, which states:
...
Invoking the signal command is not the same as invoking the kill utility from
the shell. Sending a signal with kill causes GDB to decide what to do with the
signal depending on the signal handling tables (see Signals). The signal
command passes the signal directly to your program. 
...

I'm not sure whether the documentation needs to be updated, or gdb needs to be
fixed (and indeed, can be fixed).

-- 
You are receiving this mail because:
You are on the CC list for the bug.