From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29903 invoked by alias); 5 Apr 2004 21:36:51 -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 29881 invoked from network); 5 Apr 2004 21:36:46 -0000 Received: from unknown (HELO smtp6.mindspring.com) (207.69.200.110) by sources.redhat.com with SMTP; 5 Apr 2004 21:36:46 -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 1BAblh-0002IL-00; Mon, 05 Apr 2004 17:36:33 -0400 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 694CA4B104; Mon, 5 Apr 2004 17:36:26 -0400 (EDT) To: mec.gnu@mindspring.com, zack@codesourcery.com Subject: Re: gcc HEAD, stabs+, TYPE_CODE_INT problem Cc: drow@false.org, ezannoni@redhat.com, gdb@sources.redhat.com, jimb@redhat.com Message-Id: <20040405213626.694CA4B104@berman.michael-chastain.com> Date: Mon, 05 Apr 2004 21:36:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-04/txt/msg00034.txt.bz2 Zack Weinberg writes: > Not emitting them was unintentional, and I imagine getting them back > would be straightforward. ... Would you please file a bug report > against GCC, and assign it to me? And any further investigation you > could do would be greatly appreciated. Cool. I've got a bug report all set to file, except that it looks like the httpd on gcc.gnu.org just crashed! :-( You'll have it soon. The bug does not happen with gcc gcc-3_4-branch so I agree it is lesser priority than any 3.4 activity. BTW, dwarf-2 is okay. I saw no regressions with gdb 6.0, gdb test suite 6.0, gcc HEAD, and dwarf-2. Michael C