This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/14674] No KeyboardInterrupt exception during gdb.execute
- From: "m at bruenink dot de" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 22 Jan 2013 09:39:04 +0000
- Subject: [Bug python/14674] No KeyboardInterrupt exception during gdb.execute
- Auto-submitted: auto-generated
- References: <bug-14674-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14674
--- Comment #2 from Marc BrÃnink <m at bruenink dot de> 2013-01-22 09:39:04 UTC ---
I think the second C-c should raise a KeyboardInterrupt. At least as long as I
don't change how SIGINTs are handled.
At the moment it depends on which statement your python script is executing
when you hit C-c. You cannot have a single try block and catch C-c. Instead you
need a try block and similar code in the stop_handler.
I assume a user always expects the same behaviour. Thus, I think it is not
optimal that I have to handle C-c at 2 different locations.
--
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.