From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@palves.net>
Cc: Tom de Vries <tdevries@suse.de>, Tom Tromey <tromey@adacore.com>,
Pedro Alves via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/3] Consistently use BFD's time
Date: Mon, 24 Aug 2020 13:04:40 -0700 [thread overview]
Message-ID: <20200824200440.GK24789@adacore.com> (raw)
In-Reply-To: <8548d40d-cf0f-482c-85d2-cfec7585d13f@palves.net>
Hi Pedro,
> >> For the short-term solution, I think the best compromise is to patch
> >> gnulib like Tom suggests. We have the infrastructure to do that and
> >> maintain the patch for as long as it takes to discuss the proper
> >> solution (personally, I think the only way forward for the better
> >> solution will require a live discussion; I am happy to help set that
> >> up if people would find it useful).
> >
> > I discussed it live with Tom. We don't have the time to work on this
> > right now, so we'll send a patch in a week or so. Given that everyone
> > has had a a lot of time to provide feedback on that thread, and given
> > the fact that we want to fix this before we branch, I don't think we
> > want to wait too long before getting that patch in -- assuming we are
> > still short on a better long term solution.
> >
>
> FWIW, I've tried to look at this more than once the past weeks,
> including today, hoping I'd find some nice solution, but all I got
> was a headache.
Yeah, cannot say I am surprised :-(, although I was thinking you might
be in posessions of some superpowers that made you able to find
a solution I couldn't. The fact that we have this hybrid situation
where GDB uses gnulib but one of its depedencies doesn't makes the use
of stat intractable, and if even you are having difficulties with it,
I think our only realistic options are to take a more radical approach,
either:
- Stop using the stat module from gnulib (which I think we said
we want to keep); or
- Patch the gnulib implementation for now to block the incompatible
behavior.
The idea with this approach is that we'd try to work with gnulib
maintainers to see if we could agree on a way to make the
incompatibility conditional on something. That would be our way
to eliminate this local change.
- Something else?
--
Joel
next prev parent reply other threads:[~2020-08-24 20:04 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 21:10 [PATCH 0/3] Fix gdb's BFD cache Tom Tromey
2020-01-14 21:10 ` [PATCH 1/3] Avoid hash table corruption in gdb_bfd.c Tom Tromey
2020-01-14 22:26 ` Christian Biesinger via gdb-patches
2020-01-14 21:10 ` [PATCH 2/3] Consistently use BFD's time Tom Tromey
2020-01-14 23:17 ` Christian Biesinger via gdb-patches
2020-01-15 17:51 ` Eli Zaretskii
2020-01-16 20:47 ` Pedro Alves
2020-01-16 21:58 ` Christian Biesinger via gdb-patches
2020-01-16 22:31 ` Pedro Alves
2020-01-17 8:48 ` Eli Zaretskii
2020-01-17 18:32 ` Tom Tromey
2020-01-17 21:03 ` Tom Tromey
2020-01-18 11:07 ` Eli Zaretskii
2020-01-20 15:52 ` Pedro Alves
2020-01-20 15:53 ` Pedro Alves
2020-01-20 20:50 ` Eli Zaretskii
2020-01-20 20:58 ` Pedro Alves
2020-01-21 15:50 ` Pedro Alves
2020-01-21 19:38 ` Eli Zaretskii
2020-01-21 17:56 ` Eli Zaretskii
2020-01-23 22:05 ` Tom Tromey
2020-06-19 17:51 ` Tom Tromey
2020-04-01 20:20 ` Tom Tromey
2020-06-18 14:14 ` Tom Tromey
2020-06-18 15:04 ` Eli Zaretskii
2020-06-18 16:00 ` Tom Tromey
2020-06-18 17:27 ` Eli Zaretskii
2020-06-18 17:32 ` Pedro Alves
2020-06-18 17:54 ` Eli Zaretskii
2020-06-19 12:02 ` Pedro Alves
2020-06-19 12:13 ` Eli Zaretskii
2020-06-19 17:09 ` Tom Tromey
2020-06-19 20:24 ` Tom Tromey
2020-06-19 23:05 ` Pedro Alves
2020-07-21 19:39 ` Tom Tromey
2020-07-28 19:31 ` Tom Tromey
2020-08-13 12:15 ` Tom de Vries
2020-08-14 23:40 ` Joel Brobecker
2020-08-23 16:09 ` Joel Brobecker
2020-08-23 23:32 ` Pedro Alves
2020-08-24 20:04 ` Joel Brobecker [this message]
2020-09-02 14:45 ` Tom Tromey
2020-09-02 14:59 ` Joel Brobecker
2020-06-18 17:57 ` Tom Tromey
2020-01-14 22:13 ` [PATCH 3/3] Further simplify gdb BFD caching Tom Tromey
2020-01-23 22:30 ` Tom Tromey
2020-09-02 18:45 ` 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=20200824200440.GK24789@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=tdevries@suse.de \
--cc=tromey@adacore.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