public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "chgenly at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30017] New: Cygwin gdb fails when given a windows absolute path
Date: Tue, 17 Jan 2023 19:25:46 +0000	[thread overview]
Message-ID: <bug-30017-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30017
           Summary: Cygwin gdb fails when given a windows absolute path
           Product: gdb
           Version: 11.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: chgenly at gmail dot com
  Target Milestone: ---

This is a problem on cygwin.  Launch the cygwin gdb, give it an windows
absolute path to an executable.  From the output you'll see the symbol table is
loaded, so gdb understands the path.  Yet, when attempting to run the program,
it fails to create the process.

A previous version, 9.2-1, works.

To reproduce the problem, run the following shell script from a cygwin
terminal.

echo Create main.c
cat >main.c <<END
#include <stdio.h>
int main(int argc, char**argv) {
   printf("Hello world!");
}
END
echo Compile main.c to main.exe
gcc main.c -o main
cmd="gdb $(cygpath -wa main.exe)"
echo $cmd
$cmd <<END
run
q
END

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

             reply	other threads:[~2023-01-17 19:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 19:25 chgenly at gmail dot com [this message]
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
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@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).