From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 62117 invoked by alias); 28 Feb 2020 19:49:10 -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 62109 invoked by uid 89); 28 Feb 2020 19:49:10 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=HX-Received:a50, blame, recreated X-HELO: us-smtp-1.mimecast.com Received: from us-smtp-delivery-1.mimecast.com (HELO us-smtp-1.mimecast.com) (207.211.31.120) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 28 Feb 2020 19:49:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1582919347; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=XlwFJkCRTGNXnUovXCl0I3v0QPLPgxpw/sA4s1SgRps=; b=Wczc7CxkC/V5XuEamioLeRsw4c8K3O3LspkXuWCPSWwa9ePs8aRKu+829fBDN4iF8tYBM+ D7WNsYLrK7Jd5OCKw2moQMiOv8IPWZqjykOK/Lb3XBlDryibJ1rUzlH6hhyP8iIsAWq3Rd 1V5YrLFbV7HZu7wm6jCsF+A8POhq6KM= Received: from mail-ed1-f70.google.com (mail-ed1-f70.google.com [209.85.208.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-117-FeFbDE0TNZ6arvTa3_6_lg-1; Fri, 28 Feb 2020 14:49:06 -0500 Received: by mail-ed1-f70.google.com with SMTP id y4so3066425edm.0 for ; Fri, 28 Feb 2020 11:49:05 -0800 (PST) Return-Path: Received: from ?IPv6:2001:8a0:f909:7b00:56ee:75ff:fe8d:232b? ([2001:8a0:f909:7b00:56ee:75ff:fe8d:232b]) by smtp.gmail.com with ESMTPSA id i31sm607676edi.42.2020.02.28.11.49.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 28 Feb 2020 11:49:03 -0800 (PST) Subject: Re: [PATCH 2/6] Don't reset errno/bfd_error on 'throw_perror_with_name' To: Sergio Durigan Junior , GDB Patches References: <20190926042155.31481-1-sergiodj@redhat.com> <20200226200542.746617-1-sergiodj@redhat.com> <20200226200542.746617-3-sergiodj@redhat.com> Cc: Tom Tromey , Eli Zaretskii , Ruslan Kabatsayev From: Pedro Alves Message-ID: Date: Fri, 28 Feb 2020 19:49:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <20200226200542.746617-3-sergiodj@redhat.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2020-02/txt/msg01070.txt.bz2 On 2/26/20 8:05 PM, Sergio Durigan Junior wrote: > > git blame tells me that this piece of code is pretty old; the commit > that "introduced" it is: > > commit c906108c21474dfb4ed285bcc0ac6fe02cd400cc > Author: Stan Shebs > Date: Fri Apr 16 01:35:26 1999 +0000 > > Initial creation of sourceware repository > > so yeah... This is not the oldest commit in the tree. Using git log starting at the hash, you should be able to find older commits which touch the file. The thing is that history around the time of that "initial creation" commit, is quite messy, because the CVS tree back then was deleted and recreated a number of times and merged in some odd ways. Thanks, Pedro Alves