From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30]) by sourceware.org (Postfix) with ESMTPS id 95D98385DC2B for ; Sat, 4 Apr 2020 22:31:03 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 95D98385DC2B Received: by mail-qv1-xf30.google.com with SMTP id bu9so5555025qvb.13 for ; Sat, 04 Apr 2020 15:31:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=xjUk4JxZmWSBFD+treRt2ObmqCw+t3N8vSPbROWQCzs=; b=hV539oGmUMtPf2r//3F8OSNBElVxYaK+wcwGkbJ5IcxLUqk0OGVL0cVErwmysJtAUS CiMNuUJr6+LJd41lCJVpDETI8kfrrutsqFr5zkUGn1HePy3a6OkHDL4cU59tcFczDoxe s0faTuYNK32BwluF4MMkWR5poms+eAJmv1KXOGPNiOhMf2DjjJaOcBNrL6lUUEjJSm8E HxM/1KAvARXX8t6JRGtx1Qn9AbfZm0FEn9I9FpbV5I5x3GpBpXRiZFPQyuuDG/+4chJk KSrtNN/gYz6kA1hX3Ncm/XjMF3lzJFcm0h7Jp1wAHrKivZ0tisjCaphiz6OIYt9oZraj sMQQ== X-Gm-Message-State: AGi0PuZCfL/vEZeUzAE0t3P9gXGHRuDujyZ+vlzjulL0ZyFqhDF8TuSF jy3A7wmsyK4TM452uVZrR/T3Jg== X-Google-Smtp-Source: APiQypL1NajeBdylQBIvRKyP8Vanaw0dq5RhqN66sCV7LdhKZeH13w2R+AOqhyGnQOQdl6ezRTPMUg== X-Received: by 2002:a05:6214:138a:: with SMTP id g10mr14774199qvz.231.1586039463201; Sat, 04 Apr 2020 15:31:03 -0700 (PDT) Received: from [192.168.0.181] ([179.185.146.158]) by smtp.gmail.com with ESMTPSA id 206sm10527601qkn.36.2020.04.04.15.31.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 04 Apr 2020 15:31:02 -0700 (PDT) Subject: Re: [PATCHv5] Fix range end handling of inlined subroutines From: Luis Machado To: Bernd Edlinger , "gdb-patches@sourceware.org" , Andrew Burgess , Tom Tromey References: Message-ID: <32bbd32e-7868-d102-1a72-42efafad5aef@linaro.org> Date: Sat, 4 Apr 2020 19:30:59 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-11.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Apr 2020 22:31:04 -0000 On 4/4/20 7:27 PM, Luis Machado wrote: > Hi, > > On 4/4/20 4:50 PM, Bernd Edlinger wrote: >> Hi, >> >> this is an updated version of my patch that was originally only intended >> to fix the issues with inline functions in the same file.  That needed >> re-basing anyway, because of a merge conflict. >> >> I removed the code that does the special handling of end sequence >> markers in record_line now, since it seems to cause more problems than >> it solves. >> >> I believe it will fix the regression that Louis pointed out, and >> should fix the regression that Andrew wanted to fix with his >> patch: > > I gave this a try and the FAIL's are still there unfortunately. Actually, there are 6 more of them, with the patch. I'll read through the thread to understand what these changes are aiming to fix. I wouldn't be surprised if GDB is covering some known compiler debug info generation hiccup.