From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x841.google.com (mail-qt1-x841.google.com [IPv6:2607:f8b0:4864:20::841]) by sourceware.org (Postfix) with ESMTPS id 3F82B3857C47 for ; Wed, 26 Aug 2020 18:02:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3F82B3857C47 Received: by mail-qt1-x841.google.com with SMTP id 92so2154828qtb.6 for ; Wed, 26 Aug 2020 11:02:09 -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:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=/2dQb31mHcLV//4vJLOw08pOe4SRe4Je84DdeENa32I=; b=Cn9hT831MjkJb6+8r29V/8y0VKX8TfQHTZEzCVM3/lariFO+bEa+EkfVD51I8hypkm jZBiniss6Fb1IX91QljuNON80SxISDw7en49dLNM0tW2eDWPmu2OjvJENY35SzjHv/un lqLZfSx+vpkKx5yYORpAfbBp1UJ32ohy34XQV4XJQnLitPwWvL7ni+EFj8CWFkJlp+fG ij4nupAC2RsjcL0C7/1wztfh7wd3i92dEqO6rNQwuXVTZ1SUP0O0W7LjuY9BT13vJnhW QS1hU6V5vSK1uVZ63ID10qjU4YTATrZ1Q0OUDRMI9Wq+6JLjbKSgCRF/48STek7zGQWR UY4A== X-Gm-Message-State: AOAM5328ukebxYC1luxnntWodrs/DaHdjT+RmNlq4k2+01OPVbkV4boD ZUAZjW1kdo+0VxB3dGj/fwXYp/8GymkMkA== X-Google-Smtp-Source: ABdhPJxpBxi63ER+JEObjrnbZlGC0pivp0YnyzClwVvsvPJhhLYHiefM017OZXNM4jP5zighCnmUIg== X-Received: by 2002:ac8:2ab9:: with SMTP id b54mr15014662qta.323.1598464928607; Wed, 26 Aug 2020 11:02:08 -0700 (PDT) Received: from ?IPv6:2804:7f0:8283:a3ee:e9bf:339b:4e41:8084? ([2804:7f0:8283:a3ee:e9bf:339b:4e41:8084]) by smtp.gmail.com with ESMTPSA id 95sm2630119qtc.29.2020.08.26.11.02.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 26 Aug 2020 11:02:08 -0700 (PDT) Subject: Re: [PATCH] Work around incorrect/broken pathnames in NT_FILE note To: Kevin Buettner Cc: gdb-patches@sourceware.org References: <20200807222044.2252664-1-kevinb@redhat.com> <20200809011943.77cee462@f32-m1.lan> <20200811100210.49acf4c8@f32-m1.lan> <20200811125758.4d9748a6@f32-m1.lan> From: Luis Machado Message-ID: Date: Wed, 26 Aug 2020 15:02:04 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20200811125758.4d9748a6@f32-m1.lan> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, 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: Wed, 26 Aug 2020 18:02:10 -0000 Hi, On 8/11/20 4:57 PM, Kevin Buettner wrote: > On Tue, 11 Aug 2020 14:21:53 -0300 > Luis Machado wrote: > >> On 8/11/20 2:02 PM, Kevin Buettner wrote: >>> On Sun, 9 Aug 2020 01:19:43 -0700 >>> Kevin Buettner via Gdb-patches wrote: >>> >>>> That new failure is expected in your docker environment. It might >>>> be possible to XFAIL it. We need to be able to detect that we're >>>> running in docker with the AUFS storage driver. Since we know that >>>> the kernel is leaking docker host paths, we should see these when the >>>> "info proc mappings" command is used with a loaded core file. I'll >>>> give it a try... >>> >>> It turned out that there's an even easier way to XFAIL this case. >>> See below... >> >> Great! I tried this and it looks sane. I get one XFAIL in >> gdb.base/corefile.exp and full passes on gdb.base/corefile2.exp. > > Excellent. Thanks for testing it in your environment. Just for the record, this also fixes a couple failures I noticed today in gdb.threads/corethreads.exp, where GDB doesn't print the thread id properly. This is another fallout of the broken pathnames situation.