Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH 3/3] Cache the result of find_file_and_directory
Date: Sat, 4 Dec 2021 22:47:24 -0500	[thread overview]
Message-ID: <adfcb528-41f9-3da0-2d19-9e4acfb0d4a4@polymtl.ca> (raw)
In-Reply-To: <87k0gju31v.fsf@tromey.com>



On 2021-12-04 22:46, Tom Tromey wrote:
> Simon> I see these failures on Ubuntu 20.04, when building with
> Simon> AddressSanitizer, starting with this patch.
> 
> Sorry about that.  I'll fix it soon.  Or you can back it out if you
> prefer.
> 
> Tom
> 

I'm not personally affected so I do not mind, I can wait for the fix.

Thanks!

Simon

  reply	other threads:[~2021-12-05  3:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30  1:33 [PATCH 0/3] Refactor find_file_and_directory Tom Tromey
2021-11-30  1:33 ` [PATCH 1/3] Remove Irix case from find_file_and_directory Tom Tromey
2021-12-04 10:43   ` Joel Brobecker via Gdb-patches
2021-11-30  1:33 ` [PATCH 2/3] Move file_and_directory to new file and C++-ize Tom Tromey
2021-11-30 16:18   ` Lancelot SIX via Gdb-patches
2021-11-30 17:44     ` Tom Tromey
2021-12-04 10:38   ` Joel Brobecker via Gdb-patches
2021-12-04 18:22     ` Tom Tromey
2021-11-30  1:33 ` [PATCH 3/3] Cache the result of find_file_and_directory Tom Tromey
2021-12-04 10:42   ` Joel Brobecker via Gdb-patches
2021-12-04 18:22     ` Tom Tromey
2021-12-05  2:31       ` Simon Marchi via Gdb-patches
2021-12-05  3:46         ` Tom Tromey
2021-12-05  3:47           ` Simon Marchi via Gdb-patches [this message]
2021-12-05 20:17             ` Tom Tromey
2021-12-06  1:54               ` Simon Marchi via Gdb-patches
2021-12-07  4:30                 ` Tom Tromey

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=adfcb528-41f9-3da0-2d19-9e4acfb0d4a4@polymtl.ca \
    --to=gdb-patches@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=simon.marchi@polymtl.ca \
    --cc=tom@tromey.com \
    /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