From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8909 invoked by alias); 5 Apr 2002 02:17:59 -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 8881 invoked from network); 5 Apr 2002 02:17:56 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 5 Apr 2002 02:17:56 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id g352Hp103143; Thu, 4 Apr 2002 20:17:51 -0600 Date: Thu, 04 Apr 2002 18:17:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200204050217.g352Hp103143@duracef.shout.net> To: drow@mvista.com, ezannoni@redhat.com Subject: Re: [RFA] import drow dbxread.c fix to branch Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com X-SW-Source: 2002-04/txt/msg00146.txt.bz2 Maybe I am some e-mails behind here. But: if "gcc sometimes emits line directives with a linenumber of 0", we may have a conflict. FredF's patch synthesizes entries with a line number of 0. So far DanielJ's patches have been adhering to the new meaning per FredF. Michael C 2002-02-21 Fred Fish * dbxread.c (process_one_symbol): When finding an N_FUN symbol that marks the end of the range of a function, enter a line number entry that has a line number of zero and a PC offset that matches the end of the function. This starts a range of PC's for which no line number information is known. * symtab.c (find_pc_sect_line): If our best fit is in a range of PC's for which no line number info is found (line number is zero) then we didn't find any valid line information. * symtab.h: Document use of zero line number entry.