From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26997 invoked by alias); 12 Dec 2002 01:48:12 -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 26990 invoked from network); 12 Dec 2002 01:48:11 -0000 Received: from unknown (HELO lacrosse.corp.redhat.com) (66.187.233.200) by sources.redhat.com with SMTP; 12 Dec 2002 01:48:11 -0000 Received: from free.redhat.lsd.ic.unicamp.br (aoliva2.cipe.redhat.com [10.0.1.156]) by lacrosse.corp.redhat.com (8.11.6/8.9.3) with ESMTP id gBC1m9N09186; Wed, 11 Dec 2002 20:48:09 -0500 Received: from free.redhat.lsd.ic.unicamp.br (localhost.localdomain [127.0.0.1]) by free.redhat.lsd.ic.unicamp.br (8.12.5/8.12.5) with ESMTP id gBC1m8LL024486; Wed, 11 Dec 2002 23:48:08 -0200 Received: (from aoliva@localhost) by free.redhat.lsd.ic.unicamp.br (8.12.5/8.12.5/Submit) id gBC1m8qi024482; Wed, 11 Dec 2002 23:48:08 -0200 To: Elena Zannoni Cc: gdb-patches@sources.redhat.com Subject: Re: non-contiguous files break dwarf2 init-file recognition References: <15863.48536.252516.926020@localhost.redhat.com> From: Alexandre Oliva Organization: GCC Team, Red Hat Date: Wed, 11 Dec 2002 20:36:00 -0000 In-Reply-To: <15863.48536.252516.926020@localhost.redhat.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-12/txt/msg00391.txt.bz2 On Dec 11, 2002, Elena Zannoni wrote: > http://sources.redhat.com/ml/gdb-patches/2001-12/msg00616.html > Would that patch help you here? > Probably not. Definitely not. The case at hand has debugging info for a function whose oddly-named section was explicitly discarded by a linker script, but whose lowpc was not at the beginning of the section, so, even though the section address ended up as zero, it wasn't zero for lowpc of the function, so the lowpc==0 test in dwarf2_get_pc_bounds() didn't pass and the debugging info for the function was not discarded. Then, since the comp_unit had code in .text too, the final lowpc/highpc region contained all code from zero to the end of the .text code in the comp_unit, and the program entry point happened to be in between, so we thought that comp_unit was the entry_file, and the excessively-inclusive region ended up being used to tell whether a stack trace had got to the top of the stack. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org} CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist Professional serial bug killer