This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/13265] SIGINT handling
- From: "khooyp at cs dot umd.edu" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 10 Jan 2012 21:06:18 +0000
- Subject: [Bug python/13265] SIGINT handling
- Auto-submitted: auto-generated
- References: <bug-13265-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13265
--- Comment #3 from Khoo Yit Phang <khooyp at cs dot umd.edu> 2012-01-10 21:06:18 UTC ---
Thanks for the tip: I'll post to gdb-patches with a link back here.
As for the cleanup-creating function (gdbpy_suspend_sigint_handler), note that
when it calls gdbpy_resume_sigint_handler, it does not restore the original
SIGINT handler but whatever SIGINT handler that is installed at cleanup. The
idea was that, if some nested function call changes the SIGINT handler, that
should be propagated back down the call stack as well. As it is, I don't know
whether the SIGINT handler is ever changed under normal operation, so there
won't be any observable difference in behavior between my implementation and
your suggestion.
I'll update my patch with a comment to explain the above in a moment.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.