From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Ingham To: , Keith Seitz Cc: Subject: Re: prompt in console window Date: Thu, 15 Jun 2000 10:35:00 -0000 Message-id: References: X-SW-Source: 2000-q2/msg00276.html Nicholas, Control-C actually means copy in the console window, as God intended :-) However, wiring up the stop button so that it would also interrupt macros might not be a bad idea... Or using Control-. or escape are other good options. Remember also that in most GUI applications, Control-C does not generate a SIGINT, since the GUI wants to handle all the key sequences itself. So to interrupt a macro while it is running, gdb would have to be giving control periodically back to the GUI. Don't know whether this is true or not... Jim > Hmm... perhaps I can ask an easier question. The only reason that I wanted > to get the prompt_for_continue prompt back was that I wanted a way to stop > a gdb macro (the kind that are defined in the .gdbinit file) that had > started running, in case it was taking too long and I didn't care about the > rest of the output. With the command-line gdb, you could type Ctrl-C at > that prompt to stop whatever was running, including a macro. Would it be > easier (and more helpful to the rest of the world) to get Ctrl-C working in > the console window instead of the unnecessary prompt?