public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa 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: Sat, 13 Apr 2024 11:15:07 +0000 [thread overview]
Message-ID: <bug-31636-4717-DVK24d11kX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31636-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31636
--- Comment #5 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Peter Damianov from comment #3)
> Can confirm that adding -D__MINGW_USE_VC_2005_COMPAT in CFLAGS and CXXFLAGS
> appears to resolve this issue.
Yes, I would have suggested a similar workaround for now (though using CPPFLAGS
instead of CFLAGS/CXXFLAGS).
I was wondering why this problem didn't appear in gdb-13 as well, it already
contained this define since this gnulib update:
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=dc6c21dabfbd242616b9e6266b459eded2d0762b
It's because reread_symbols() of gdb/symfile.c changed from stat() to
bfd_stat() here:
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=f2c4f78c813a9cef38b7e9c9ad18822fb9e19345
Should bfd be changed to always define __MINGW_USE_VC2005_COMPAT for mingw
targets like gnulib does?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-04-13 11:15 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 [this message]
2024-04-19 20:44 ` tromey at sourceware dot org
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-DVK24d11kX@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).