From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Work around incorrect/broken pathnames in NT_FILE note
Date: Mon, 31 Aug 2020 19:03:34 -0700 [thread overview]
Message-ID: <20200831190334.41b22928@f32-m1.lan> (raw)
In-Reply-To: <20200811100210.49acf4c8@f32-m1.lan>
On Tue, 11 Aug 2020 10:02:10 -0700
Kevin Buettner <kevinb@redhat.com> wrote:
> From 23452e31502820e15c1c72a3935360f7f1932ed9 Mon Sep 17 00:00:00 2001
> From: Kevin Buettner <kevinb@redhat.com>
> 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
next prev parent reply other threads:[~2020-09-01 2:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 22:20 Kevin Buettner
2020-08-08 10:19 ` Luis Machado
2020-08-09 8:19 ` Kevin Buettner
2020-08-11 17:02 ` Kevin Buettner
2020-08-11 17:21 ` Luis Machado
2020-08-11 19:57 ` Kevin Buettner
2020-08-26 18:02 ` Luis Machado
2020-09-01 2:03 ` Kevin Buettner [this message]
2020-08-20 14:57 ` Pedro Alves
2020-08-29 3:25 ` Kevin Buettner
2020-08-31 14:50 ` Pedro Alves
2020-09-01 2:04 ` Kevin Buettner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200831190334.41b22928@f32-m1.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox