Re: [PATCH] Work around incorrect/broken pathnames in NT_FILE note

[Luis Machado <luis.machado@linaro.org>]

Hi,

On 8/11/20 4:57 PM, Kevin Buettner wrote:
> 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.

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.