public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30017] Cygwin gdb fails when given a windows absolute path
Date: Tue, 07 Mar 2023 00:54:34 +0000 [thread overview]
Message-ID: <bug-30017-4717-eYArKcgI57@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30017-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30017
--- Comment #3 from Jonah Graham <jonah at kichwacoders dot com> ---
Thanks Jon for the analysis.
> but some one who cares about this edge-case will have to write it.
I think that is the problem we are facing now as to who will solve this
problem. For the last ~20 years it turns out that CDT was relying on undefined
behaviour in Cygwin/GDB that changed in GDB 10.
We are going to track that work in CDT here
https://github.com/eclipse-cdt/cdt/issues/228 but at the moment no one is
allocated to it, but here is hoping that someone steps forward. I have given
guidance of where someone could start in CDT.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-07 0:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 19:25 [Bug gdb/30017] New: " chgenly at gmail dot com
2023-01-17 19:33 ` [Bug gdb/30017] " jonah at kichwacoders dot com
2023-01-19 19:49 ` chgenly at gmail dot com
2023-03-05 12:45 ` jon.turney at dronecode dot org.uk
2023-03-07 0:54 ` jonah at kichwacoders dot com [this message]
2023-03-07 21:53 ` jon.turney at dronecode dot org.uk
2023-03-19 16:46 ` jon.turney at dronecode dot org.uk
2023-03-22 18:13 ` jonah at kichwacoders dot com
2023-03-22 20:43 ` jon.turney at dronecode dot org.uk
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-30017-4717-eYArKcgI57@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).