From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15470 invoked by alias); 21 Nov 2014 07:41:29 -0000 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 Received: (qmail 15449 invoked by uid 89); 21 Nov 2014 07:41:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout23.012.net.il Received: from mtaout23.012.net.il (HELO mtaout23.012.net.il) (80.179.55.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 21 Nov 2014 07:41:27 +0000 Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0NFD00G00P4RQX00@a-mtaout23.012.net.il> for gdb-patches@sourceware.org; Fri, 21 Nov 2014 09:41:24 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NFD00G7OPD0R700@a-mtaout23.012.net.il>; Fri, 21 Nov 2014 09:41:24 +0200 (IST) Date: Fri, 21 Nov 2014 07:41:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH 2/4] python support for fetching separate debug files: have_debug_info In-reply-to: To: Doug Evans Cc: gdb-patches@sourceware.org, palves@redhat.com, sergiodj@redhat.com Reply-to: Eli Zaretskii Message-id: <837fyp57bu.fsf@gnu.org> References: X-IsSubscribed: yes X-SW-Source: 2014-11/txt/msg00498.txt.bz2 > From: Doug Evans > Date: Thu, 20 Nov 2014 13:22:39 -0800 > > This patch provides an API call to determine whether debug information > is present. It's based on the same test that gdb internally uses > to decide whether to look for separate debug files. OK for the documentation parts. Btw, I wonder why this is useful, given this caveat: > +Note that a program compiled without @samp{-g} may still have some debug > +information, e.g., from the @code{C} runtime. Thus a value of @code{True} > +for this attribute does not mean that debug information is present for > +every source file in the program. It only means that debug information > +is present for at least one source file. If this attribute cannot be relied upon, why is it a good idea to expose it to Python?