This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/20485] sigprocmask in tracee affects tracer as well
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 17 Aug 2016 23:24:52 +0000
- Subject: [Bug gdb/20485] sigprocmask in tracee affects tracer as well
- Auto-submitted: auto-generated
- References: <bug-20485-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20485
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
> But it should not forward it! When asking gdb for the signal configuration:
That's not forwarding the signal to the tracee. That would be a ptrace call
with a non-zero signal argument. That's gdb trying to interrupt the program
with an asynchronous SIGINT, with the idea that ptrace intercepts that SIGINT,
returning control of the tracee back to gdb. The inferior never sees that
SIGINT -- try the same with an inferior that doesn't block SIGINT.
Now, the original problem is that if SIGINT is blocked, the kernel/ptrace does
not intercept ctrl-c/SIGINT, simply because one isn't generated at all.
See bug #15250, bug #14559 and bug #9425.
--
You are receiving this mail because:
You are on the CC list for the bug.