From: Kevin Buettner <kevinb@redhat.com>
To: Luis Machado <luis.machado@linaro.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Work around incorrect/broken pathnames in NT_FILE note
Date: Tue, 11 Aug 2020 12:57:58 -0700 [thread overview]
Message-ID: <20200811125758.4d9748a6@f32-m1.lan> (raw)
In-Reply-To: <b12c4099-16a2-ecd6-8111-e828e6e4aa03@linaro.org>
On Tue, 11 Aug 2020 14:21:53 -0300
Luis Machado <luis.machado@linaro.org> 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 <gdb-patches@sourceware.org> 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
next prev parent reply other threads:[~2020-08-11 19:58 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 [this message]
2020-08-26 18:02 ` Luis Machado
2020-09-01 2:03 ` Kevin Buettner
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=20200811125758.4d9748a6@f32-m1.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@linaro.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