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 [207.211.31.120]) by sourceware.org (Postfix) with ESMTP id CA6A73857C42 for ; Tue, 1 Sep 2020 02:03:38 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org CA6A73857C42 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-529-ExyXkyTZOdi0lDpyUzv18g-1; Mon, 31 Aug 2020 22:03:36 -0400 X-MC-Unique: ExyXkyTZOdi0lDpyUzv18g-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id ACF94801AC5; Tue, 1 Sep 2020 02:03:35 +0000 (UTC) Received: from f32-m1.lan (ovpn-115-29.phx2.redhat.com [10.3.115.29]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 81D2638A; Tue, 1 Sep 2020 02:03:35 +0000 (UTC) Date: Mon, 31 Aug 2020 19:03:34 -0700 From: Kevin Buettner To: gdb-patches@sourceware.org Subject: Re: [PATCH] Work around incorrect/broken pathnames in NT_FILE note Message-ID: <20200831190334.41b22928@f32-m1.lan> In-Reply-To: <20200811100210.49acf4c8@f32-m1.lan> 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.84 on 10.5.11.23 X-Mimecast-Spam-Score: 0.002 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.2 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_H2, 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, 01 Sep 2020 02:03:40 -0000 On Tue, 11 Aug 2020 10:02:10 -0700 Kevin Buettner wrote: > From 23452e31502820e15c1c72a3935360f7f1932ed9 Mon Sep 17 00:00:00 2001 > From: Kevin Buettner > Date: Tue, 11 Aug 2020 09:36:12 -0700 > Subject: [PATCH] corefile.exp: XFAIL warning-free test when testing on docker > > When testing on docker using the AUFS storage driver, loading a core > file will often print a number of warnings. Here's an example (with > the pathname shortened somewhat): > > warning: Can't open file /var/lib/docker/aufs/diff/d07..e21/lib/x86_64-linux-gnu/libc-2.27.so during file-backed mapping note processing > > The "warning-free" test in gdb.base/corefile.exp will fail if any > warnings are printed, but this particular warning is unavoidable when > running in the docker environment. Fortunately, the path mentions > both "docker" and "aufs", making it easy to XFAIL this case. > > gdb/testsuite/ChangeLog: > > * gdb.base/corefile.exp (warning-free): XFAIL test when running > on docker w/ AUFS storage driver. I've pushed this change. Kevin