From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32296 invoked by alias); 22 Dec 2002 23:54:48 -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 32164 invoked from network); 22 Dec 2002 23:54:48 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by 209.249.29.67 with SMTP; 22 Dec 2002 23:54:48 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id gBMNsYf27208; Sun, 22 Dec 2002 17:54:34 -0600 Date: Sun, 22 Dec 2002 16:01:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200212222354.gBMNsYf27208@duracef.shout.net> To: ezannoni@redhat.com Subject: Re: [rfa] delete 'force_return' from lookup_symbol_aux_minsyms Cc: carlton@math.stanford.edu, gdb-patches@sources.redhat.com, jimb@redhat.com X-SW-Source: 2002-12/txt/msg00625.txt.bz2 Elena Z wrote: > I am not sure if David committed it yet, but the patch it at the > bottom of: > http://sources.redhat.com/ml/gdb-patches/2002-12/msg00560.html > Maybe you already tested it! I am having some problems analyzing this. I see 3 regressions from 2002-12-18 to 2002-12-21, but I can't tell if they are gcc problems or gdb problems. I've got one set of runs with: gdb HEAD 2002-12-18 gcc HEAD 2002-12-18 And another set of runs with: gdb HEAD 2002-12-21 gcc HEAD 2002-12-21 It would be great if I kept the install directories from 2002-12-18 for a few days, but I already recycled the disk space. :( I do have all the executable files from gdb/testsuite though, so I can try the new gdb on all the executables built with gcc HEAD 2002-12-18. For the curious, the 3 regressions are: (1) gcc ICE when compiling gdb.c++/anon-union.exp with gcc HEAD 2002-12-21. and dwarf-2. This is obviously a gcc problem and I will follow the gcc reporting procedures for it. I think the problem is related to the special status of C++ "main", which must be return type int, but are not required to return a value (the compiler is required to synthesize a value if control falls off the end, which is special code in gcc, which has problems getting the debug information right). (2) New problems near the end of gdb.c++/anon-union.exp with gcc HEAD and stabs+. Probably gcc, might be gdb (unlikely). (3) Problems with gdb.c++/casts.exp. I'll go do some QA sleuthing and file bug reports and stuff. Michael C