public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31636] GDB 14 incorrectly reads/handles file timestamps on i686-w64-mingw32 hosts
Date: Fri, 19 Apr 2024 20:44:20 +0000	[thread overview]
Message-ID: <bug-31636-4717-oWJ4nEB4dk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31636-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31636

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
I think we didn't anticipate that 'struct stat' itself could
vary between subdirectories like this.

Calling bfd_stat is unavoidable and that symfile.c change was
needed to fix a different bug -- at the very least that code
would fail for remote BFDs.

I wonder if there's a hack we could add to gnulib to avoid
some of its 'stat'-related changes.  Maybe that would be
sufficient.

Otherwise I think the only two solutions here are (1) also
get BFD to use gnulib, and (2) remove gnulib.

(1) is a bit of a pain because gdb has to carefully curate
exactly which gnulib modules are used -- since IIRC there's
at least one that we accidentally used and it broke other
things.

Probably (2) is best for our long-term sanity.  And maybe simpler
now that gdb uses c++ and can perhaps defer a subset of
the portability problems to the standard library.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2024-04-19 20:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 16:08 [Bug gdb/31636] New: " peter0x44 at disroot dot org
2024-04-12 16:09 ` [Bug gdb/31636] " peter0x44 at disroot dot org
2024-04-12 16:21 ` peter0x44 at disroot dot org
2024-04-12 17:52 ` ssbssa at sourceware dot org
2024-04-12 18:11 ` pedro at palves dot net
2024-04-13  2:18 ` peter0x44 at disroot dot org
2024-04-13  2:20 ` peter0x44 at disroot dot org
2024-04-13 11:15 ` ssbssa at sourceware dot org
2024-04-19 20:44 ` tromey at sourceware dot org [this message]

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=bug-31636-4717-oWJ4nEB4dk@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).