From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28964 invoked by alias); 16 Apr 2003 15:58:24 -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 28857 invoked from network); 16 Apr 2003 15:58:22 -0000 Received: from unknown (HELO mailhub.lss.emc.com) (168.159.2.8) by sources.redhat.com with SMTP; 16 Apr 2003 15:58:22 -0000 Received: from emc.com (lul1179.lss.emc.com [168.159.33.179]) by mailhub.lss.emc.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h3GFwJV09359; Wed, 16 Apr 2003 11:58:20 -0400 (EDT) Message-Id: <200304161558.h3GFwJV09359@mailhub.lss.emc.com> To: gcc@gcc.gnu.org, gdb@sources.redhat.com Subject: stabs and macro information Date: Wed, 16 Apr 2003 15:58:00 -0000 From: David Taylor X-SW-Source: 2003-04/txt/msg00161.txt.bz2 Currently, when invoked with -gdwarf-2 -g3, gcc will record macro information in a .debug_macinfo elf section. And when presented with an executable containing macro information in a .debug_macinfo section, gdb will make use of it. Many companies, including EMC, still use stabs. So... it would be nice if the same was true of stabs. To that end, I have started to implement this. The GCC side of things took less than a day to implement; I'm hoping to get started on the GDB side soon. One question I have is what stabs types to use -- tentatively I'm using: /* GNU extension. Macro define. */ __define_stab(N_MAC_DEFINE, 0x36, "MAC_DEFINE") /* GNU extension. Macro undefine. */ __define_stab(N_MAC_UNDEF, 0x3a, "MAC_UNDEF") as it appears (based on gcc/stab.def, include/aout/stab.def, and gdb/doc/stabs.texinfo) that 0x36 and 0x3a are available. Is anyone aware of any other uses of stab types 0x36 and 0x3a -- i.e. is anyone aware of uses that might conflict? Thanks. David p.s. shouldn't include/aout/stab.def and gcc/stab.def be merged? -- David Taylor dtaylor@emc.com