From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 126799 invoked by alias); 18 Apr 2019 12:53:57 -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 126790 invoked by uid 89); 18 Apr 2019 12:53:56 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=explain X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 18 Apr 2019 12:53:55 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:59451) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hH6Y5-000470-Eo; Thu, 18 Apr 2019 08:53:53 -0400 Received: from [176.228.60.248] (port=4662 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hH6Y4-0000QK-PZ; Thu, 18 Apr 2019 08:53:53 -0400 Date: Thu, 18 Apr 2019 12:53:00 -0000 Message-Id: <83h8aveape.fsf@gnu.org> From: Eli Zaretskii To: LRN CC: gdb-patches@sourceware.org In-reply-to: <20439f48-c0ff-e4b2-5cfc-6bb4b594d88c@gmail.com> (message from LRN on Wed, 17 Apr 2019 23:06:19 +0300) Subject: Re: Warning when using separate debug info file References: <83y348edoi.fsf@gnu.org> <20439f48-c0ff-e4b2-5cfc-6bb4b594d88c@gmail.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-IsSubscribed: yes X-SW-Source: 2019-04/txt/msg00317.txt.bz2 > From: LRN > Date: Wed, 17 Apr 2019 23:06:19 +0300 > > I'm too lazy to explain this right now. Here's a Python program (attached) that > creates separate debug info files that do not produce this warning. So the workaround is to make the separate debug file have that section. Not sure it's worth the hassle, since the warning is harmless. > I've reported it to the bugtracker, but no one seems to be interested in fixing > this, and i have no idea why this happens (although i do have a hypothesis). What is your hypothesis, if I may ask? Thanks.