From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4203 invoked by alias); 17 Mar 2004 01:53:46 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 4195 invoked from network); 17 Mar 2004 01:53:42 -0000 Received: from unknown (HELO smtp6.mindspring.com) (207.69.200.110) by sources.redhat.com with SMTP; 17 Mar 2004 01:53:42 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by smtp6.mindspring.com with esmtp (Exim 3.33 #1) id 1B3QFZ-0008EY-00; Tue, 16 Mar 2004 20:53:41 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 3DA244B104; Tue, 16 Mar 2004 20:53:43 -0500 (EST) To: eliz@gnu.org, gdb-patches@sources.redhat.com Subject: [rfa/doco] PROBLEMS: add regressions since gdb 6.0 Message-Id: <20040317015343.3DA244B104@berman.michael-chastain.com> Date: Wed, 17 Mar 2004 01:53:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-03.o/txt/msg00380.txt Here is an update for PROBLEMS. I added all the regressions that I know about from gdb 6.0 to gdb 6.1. I also added some section headers, "Regressions since gdb 6.0" and "Regressions since gdb 5.3". I would like to commit this to both gdb HEAD and gdb gdb_6_1-branch. Okay to commit to HEAD? Okay to commit to the branch? Michael C 2004-03-16 Michael Chastain * PROBLEMS: Add section headers, "Regressions since gdb 6.0" and "Regressions since gdb 5.3.". Add all the regressions I know about since gdb 6.0. Index: PROBLEMS =================================================================== RCS file: /cvs/src/src/gdb/PROBLEMS,v retrieving revision 1.23 diff -u -c -3 -p -r1.23 PROBLEMS *** PROBLEMS 29 Feb 2004 02:57:24 -0000 1.23 --- PROBLEMS 17 Mar 2004 01:50:08 -0000 *************** Fortunately the ARM target, in the GDB's *** 23,28 **** --- 23,52 ---- updated so people encountering problems should consider downloading a more current GDB (http://www.gnu.org/software/gdb/current). + *** Regressions since gdb 6.0 + + gdb/826: variables in C++ namespaces have to be enclosed in quotes + + When referring to a variable in C++ code that is inside a + namespace, you have to put it inside single quotes. + + gdb/931: GDB could be more generous when reading types C++ templates on input + + When the user types a template, GDB frequently requires the type to be + typed in a certain way (e.g. "const char*" as opposed to "const char *" + or "char const *" or "char const*"). + + gdb/1505: [regression] gdb prints a bad backtrace for a thread + + When backtracing a thread, gdb doesn't stop until it hits garbage. + This is sensitive to the operating system and thread library. + + gdb/1512: no canonical way to output names of C++ types + + We currently don't have any canonical way to output names of C++ types. + E.g. "const char *" versus "char const *"; more subtleties aries when + dealing with templates. + gdb/1516: [regression] local classes, gcc 2.95.3, dwarf-2 With gcc 2.95.3 and the dwarf-2 debugging format, classes which are *************** This applies only to classes where the c *** 35,40 **** --- 59,73 ---- function, not to variables defined with types that are defined somewhere outside any function (which most types are). + 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. + + *** Regressions since gdb 5.3 + gdb/1091: Constructor breakpoints ignored gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints *************** implement virtual base classes. gcc 2.x *** 52,59 **** 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. --- 85,87 ---- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4203 invoked by alias); 17 Mar 2004 01:53:46 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 4195 invoked from network); 17 Mar 2004 01:53:42 -0000 Received: from unknown (HELO smtp6.mindspring.com) (207.69.200.110) by sources.redhat.com with SMTP; 17 Mar 2004 01:53:42 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by smtp6.mindspring.com with esmtp (Exim 3.33 #1) id 1B3QFZ-0008EY-00; Tue, 16 Mar 2004 20:53:41 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 3DA244B104; Tue, 16 Mar 2004 20:53:43 -0500 (EST) To: eliz@gnu.org, gdb-patches@sources.redhat.com Subject: [rfa/doco] PROBLEMS: add regressions since gdb 6.0 Message-ID: <20040317015343.3DA244B104@berman.michael-chastain.com> Date: Fri, 19 Mar 2004 00:09:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-03/txt/msg00380.txt.bz2 Message-ID: <20040319000900.WpvpPskg3fZ41nCyDltR_bqaJoHQLKcABPiLPKpnlMw@z> Here is an update for PROBLEMS. I added all the regressions that I know about from gdb 6.0 to gdb 6.1. I also added some section headers, "Regressions since gdb 6.0" and "Regressions since gdb 5.3". I would like to commit this to both gdb HEAD and gdb gdb_6_1-branch. Okay to commit to HEAD? Okay to commit to the branch? Michael C 2004-03-16 Michael Chastain * PROBLEMS: Add section headers, "Regressions since gdb 6.0" and "Regressions since gdb 5.3.". Add all the regressions I know about since gdb 6.0. Index: PROBLEMS =================================================================== RCS file: /cvs/src/src/gdb/PROBLEMS,v retrieving revision 1.23 diff -u -c -3 -p -r1.23 PROBLEMS *** PROBLEMS 29 Feb 2004 02:57:24 -0000 1.23 --- PROBLEMS 17 Mar 2004 01:50:08 -0000 *************** Fortunately the ARM target, in the GDB's *** 23,28 **** --- 23,52 ---- updated so people encountering problems should consider downloading a more current GDB (http://www.gnu.org/software/gdb/current). + *** Regressions since gdb 6.0 + + gdb/826: variables in C++ namespaces have to be enclosed in quotes + + When referring to a variable in C++ code that is inside a + namespace, you have to put it inside single quotes. + + gdb/931: GDB could be more generous when reading types C++ templates on input + + When the user types a template, GDB frequently requires the type to be + typed in a certain way (e.g. "const char*" as opposed to "const char *" + or "char const *" or "char const*"). + + gdb/1505: [regression] gdb prints a bad backtrace for a thread + + When backtracing a thread, gdb doesn't stop until it hits garbage. + This is sensitive to the operating system and thread library. + + gdb/1512: no canonical way to output names of C++ types + + We currently don't have any canonical way to output names of C++ types. + E.g. "const char *" versus "char const *"; more subtleties aries when + dealing with templates. + gdb/1516: [regression] local classes, gcc 2.95.3, dwarf-2 With gcc 2.95.3 and the dwarf-2 debugging format, classes which are *************** This applies only to classes where the c *** 35,40 **** --- 59,73 ---- function, not to variables defined with types that are defined somewhere outside any function (which most types are). + 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. + + *** Regressions since gdb 5.3 + gdb/1091: Constructor breakpoints ignored gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints *************** implement virtual base classes. gcc 2.x *** 52,59 **** 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. --- 85,87 ----