From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30656 invoked by alias); 19 Mar 2004 16:16:39 -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 30645 invoked from network); 19 Mar 2004 16:16:37 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 19 Mar 2004 16:16:37 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 09FBA2B92; Fri, 19 Mar 2004 11:16:36 -0500 (EST) Message-ID: <405B1CE3.2070007@gnu.org> Date: Fri, 19 Mar 2004 16:16:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: gdb-patches@sources.redhat.com Subject: [patch/rfc] Add meaningful section titles to PROBLEMS Content-Type: multipart/mixed; boundary="------------080500030803040308090609" X-SW-Source: 2004-03/txt/msg00455.txt.bz2 This is a multi-part message in MIME format. --------------080500030803040308090609 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-length: 605 Hello, This patch gets rid of the meaningless(1) "Regressions since X.X" titles replacing them with functional section titles: *** C++ support *** Stack backtraces *** Misc (I think that's all) The file is re-ordered but none of the contents change. comments? In terms of content, I think any "problem" that is there for more than one full release cycle should be documented -- that after all is where the user is ment to be looking for information. Andrew (1) For instance, the cntrl-c bug is a regression from something like 5.0 and not 6.0, it's just that it only recently got reported. --------------080500030803040308090609 Content-Type: text/plain; name="diffs" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="diffs" Content-length: 3943 2004-03-19 Andrew Cagney * PROBLEMS: Add general section titles, remove references to specific releases. Index: PROBLEMS =================================================================== RCS file: /cvs/src/src/gdb/PROBLEMS,v retrieving revision 1.24 diff -c -r1.24 PROBLEMS *** PROBLEMS 17 Mar 2004 07:00:41 -0000 1.24 --- PROBLEMS 19 Mar 2004 16:09:11 -0000 *************** *** 3,29 **** See also: http://www.gnu.org/software/gdb/bugs/ - mips*-*-* - powerpc*-*-* - sparc*-*-* ! GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated ! to use the new frame mechanism. ! People encountering problems with these targets should consult GDB's ! web pages and mailing lists (http://www.gnu.org/software/gdb/) to see ! if there is an update. ! ! arm-*-* ! ! GDB's ARM target, in 6.0, has not been updated to use the new frame ! mechanism. ! Fortunately the ARM target, in the GDB's mainline sources, has been ! 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 --- 3,19 ---- See also: http://www.gnu.org/software/gdb/bugs/ ! *** Misc ! 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. ! *** C++ support gdb/826: variables in C++ namespaces have to be enclosed in quotes *************** *** 36,46 **** 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. --- 26,31 ---- *************** *** 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 --- 44,49 ---- *************** *** 85,87 **** --- 61,89 ---- function with a hidden parameter, but gcc 3.x conforms to a multi-vendor ABI for C++ which requires multiple object code functions. + *** Stack backtraces + + 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. + + mips*-*-* + powerpc*-*-* + sparc*-*-* + + GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated + to use the new frame mechanism. + + People encountering problems with these targets should consult GDB's + web pages and mailing lists (http://www.gnu.org/software/gdb/) to see + if there is an update. + + arm-*-* + + GDB's ARM target, in 6.0, has not been updated to use the new frame + mechanism. + + Fortunately the ARM target, in the GDB's mainline sources, has been + updated so people encountering problems should consider downloading a + more current GDB (http://www.gnu.org/software/gdb/current). --------------080500030803040308090609--