From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) by sourceware.org (Postfix) with ESMTP id D4FE53857C47 for ; Tue, 11 Aug 2020 19:58:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D4FE53857C47 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-418-vT4nC8ItNXahWESrr2bsNg-1; Tue, 11 Aug 2020 15:58:00 -0400 X-MC-Unique: vT4nC8ItNXahWESrr2bsNg-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 2DDCC1030C21; Tue, 11 Aug 2020 19:57:59 +0000 (UTC) Received: from f32-m1.lan (ovpn-112-15.phx2.redhat.com [10.3.112.15]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 085AA70106; Tue, 11 Aug 2020 19:57:58 +0000 (UTC) Date: Tue, 11 Aug 2020 12:57:58 -0700 From: Kevin Buettner To: Luis Machado Cc: gdb-patches@sourceware.org Subject: Re: [PATCH] Work around incorrect/broken pathnames in NT_FILE note Message-ID: <20200811125758.4d9748a6@f32-m1.lan> In-Reply-To: References: <20200807222044.2252664-1-kevinb@redhat.com> <20200809011943.77cee462@f32-m1.lan> <20200811100210.49acf4c8@f32-m1.lan> Organization: Red Hat MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.4 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, 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: Tue, 11 Aug 2020 19:58:04 -0000 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. Kevin