Re: [RFA/PROBLEMS] Document the QUIT problem

[Joel Brobecker <brobecker@gnat.com>]

[-- Attachment #1: Type: text/plain, Size: 323 bytes --]

OK, I created a PR for this problem: gdb/1560. That made sense.

Here is what I ended up checkin in (I took Eli's previous message as an
approval of the contents of the new PROBLEMS entry).

2004-02-20  J. brobecker  <brobecker@gnat.com>

        * PROBLEMS: Add description of problem documented under gdb/1560.

-- 
Joel

[-- Attachment #2: PROBLEMS.diff --]
[-- Type: text/plain, Size: 852 bytes --]

Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.21
diff -u -p -r1.21 PROBLEMS
--- PROBLEMS	27 Jan 2004 09:46:16 -0000	1.21
+++ PROBLEMS	20 Feb 2004 21:41:11 -0000
@@ -51,3 +51,9 @@ gcc 3.x generates these multiple object 
 implement virtual base classes.  gcc 2.x generated just one object code
 function with a hidden parameter, but gcc 3.x conforms to a multi-vendor
 ABI for C++ which requires multiple object code functions.
+
+gdb/1560: Control-C does not always interrupt GDB.
+When GDB is busy processing a command which takes a long time to
+complete, hitting Control-C does not have the expected effect.
+The command execution is not aborted, and the "QUIT" message confirming
+the abortion is displayed only after the command has been completed.