From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4752 invoked by alias); 30 Dec 2003 20:57:14 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 4745 invoked from network); 30 Dec 2003 20:57:13 -0000 Received: from unknown (HELO mclean.mail.mindspring.net) (207.69.200.57) by sources.redhat.com with SMTP; 30 Dec 2003 20:57:13 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by mclean.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1AbQvS-0007y2-00 for gdb@sources.redhat.com; Tue, 30 Dec 2003 15:57:14 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id E23EB4B35A; Tue, 30 Dec 2003 15:57:20 -0500 (EST) To: gdb@sources.redhat.com Subject: gcc HEAD rearranges stabs members Message-Id: <20031230205720.E23EB4B35A@berman.michael-chastain.com> Date: Tue, 30 Dec 2003 20:57:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2003-12/txt/msg00285.txt.bz2 gcc rearranged the structure members in stabs+ debug info. Ouch! Ouch! Last week (gdb 6.0, gcc HEAD 2003-12-23, binutils 2.14, -gstabs+): ptype class Foo type = class Foo { public: int x; int y; static int st; Foo & operator=(Foo const&); Foo(Foo const&); Foo(int, int); int operator!(); operator int(); int times(int); } This week (gdb 6.0, gcc HEAD 2003-12-28, binutils 2.14, -gstabs+): ptype class Foo type = class Foo { public: int x; int y; static int st; Foo(int, int); int operator!(); operator int(); int times(int); Foo & operator=(Foo const&); Foo(Foo const&); } Same change with gdb HEAD of course. So I have to write a bunch of new patterns in gdb.cp/*.exp to match the new output. And I have to stare at all the differences and see if any actual bugs crept in along with the rearrangement. (David, this is why I like the HEAD test suite to keep working with gdb 6.0 -- because the gdb 6.0 test suite just lost a lot of value with gcc HEAD). Hey, maybe some fixes crept in. A guy can hope. Michael C