public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jon.turney at dronecode dot org.uk" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30017] Cygwin gdb fails when given a windows absolute path
Date: Sun, 19 Mar 2023 16:46:49 +0000	[thread overview]
Message-ID: <bug-30017-4717-pG5IozWpd2@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 #5 from Jon Turney <jon.turney at dronecode dot org.uk> ---
I bisected this, which lands on :

# first bad commit: [727b7b1864973c2645a554727afd0eaf1303673a] Sync config,
include and libiberty with GCC

Looking at:

https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=727b7b1864973c2645a554727afd0eaf1303673a#patch4

This makes perfect sense, but doesn't really offer a lot of immediate clues how
to fix it.

There's presumably some logic in gdb/windows-nat which uses those macros
(probably IS_ABSOLUTE_PATH given the reported problem), who's behaviour is
changed by this commit.

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

  parent reply	other threads:[~2023-03-19 16:46 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
2023-03-07 21:53 ` jon.turney at dronecode dot org.uk
2023-03-19 16:46 ` jon.turney at dronecode dot org.uk [this message]
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-pG5IozWpd2@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).