From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14280 invoked by alias); 17 Sep 2007 12:27:04 -0000 Received: (qmail 14269 invoked by uid 22791); 17 Sep 2007 12:27:03 -0000 X-Spam-Check-By: sourceware.org Received: from province.act-europe.fr (HELO province.act-europe.fr) (212.157.227.214) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 17 Sep 2007 12:26:56 +0000 Received: by province.act-europe.fr (Postfix, from userid 560) id 51732164906; Mon, 17 Sep 2007 14:26:54 +0200 (CEST) Date: Mon, 17 Sep 2007 12:27:00 -0000 From: Jerome Guitton To: gdb-patches@sourceware.org Subject: Re: [RFA] dwarf2loc, guard against null Message-ID: <20070917122654.GY93930@adacore.com> References: <20070917120443.GA21276@adacore.com> <20070917121503.GA7606@caradoc.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070917121503.GA7606@caradoc.them.org> User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-09/txt/msg00212.txt.bz2 Daniel Jacobowitz (drow@false.org): > I'm not sure - there must be another bug so it might be this should be > a gdb_assert instead. The DW_AT_frame_base that brought us here came > from .debug_info inside an entry for a function. So we must have > found the function at some point. But we didn't find the function > this time - why not? Hmmm... Let me have a closer look. In my case, the problem appears when debugging an application on VxWorks, with this scenario: * breakpoint hit; * print the address of a variable in the current frame (print &DB); * resume the execution; program exited normally; * retry to print the variable => end up in dwarf_expr_frame_base, no frame, crash. We are (probably) still using a wrong .debug_info at this point.