From: "Eli Zaretskii" <eliz@gnu.org>
To: gdb@sourceware.org
Subject: Re: Windows support in GDB
Date: Mon, 02 May 2005 19:03:00 -0000 [thread overview]
Message-ID: <01c54f49$Blat.v2.4$609aece0@zahav.net.il> (raw)
In-Reply-To: <20050501214128.GA23129@trixie.casa.cgf.cx> (message from Christopher Faylor on Sun, 1 May 2005 17:41:28 -0400)
> Date: Sun, 1 May 2005 17:41:28 -0400
> From: Christopher Faylor <me@cgf.cx>
>
> >In fact, any serious use of GDB will almost instantly bump into such a
> >consistency (or lack thereof) issue. For example, will the `edit' and
> >`shell' commands work if I don't have a Cygwin Bash installed and GDB
> >is configured to invoke that Bash as the shell?
>
> And, if they don't, what's the solution? You fix it so they will work.
> Presumably, if there is no /bin/sh.exe available, you'd use a fallback.
> You could even implement a switch to force cygwin's gdb into "windows
> path mode".
You could do all that and more, but AFAIK that'd be against the
``spirit of Cygwin'', which is to solve all incompatibilities in the
runtime, and leave the application sources more or less intact. If
you leave the application sources intact, the Unixy shell assumptions,
like the -c switch and redirection syntax, will be hard to solve
inside the library that implements fork/exec or whatever.
> I *suspect* however, that fixing cygwin's gdb to better handle
> windows paths is probably a lot less work than what Mark did.
I actually think the other way around. But I certainly don't want to
start a Cygwin-yaye-o-nay dispute.
next prev parent reply other threads:[~2005-05-02 19:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 15:32 Mark Kettenis
2005-04-29 15:32 ` Daniel Jacobowitz
2005-04-29 16:08 ` Christopher Faylor
2005-04-29 16:31 ` Mark Mitchell
2005-04-29 16:36 ` Christopher Faylor
2005-04-29 16:47 ` Mark Mitchell
2005-04-29 16:56 ` Christopher Faylor
2005-04-29 17:05 ` Mark Mitchell
2005-04-29 17:16 ` Christopher Faylor
2005-05-01 20:13 ` Eli Zaretskii
2005-05-01 19:50 ` Eli Zaretskii
2005-04-29 16:52 ` Dave Korn
2005-04-29 16:57 ` Mark Mitchell
2005-04-29 17:00 ` Dave Korn
2005-04-30 16:18 ` Mark Kettenis
2005-04-30 20:37 ` Christopher Faylor
2005-05-01 20:05 ` Eli Zaretskii
2005-05-01 20:06 ` Mark Mitchell
2005-05-01 20:24 ` Eli Zaretskii
2005-04-29 16:32 ` Kris Warkentin
2005-04-29 16:40 ` Christopher Faylor
2005-04-29 17:00 ` Kris Warkentin
2005-05-01 19:55 ` Eli Zaretskii
2005-05-01 21:41 ` Christopher Faylor
2005-05-02 19:03 ` Eli Zaretskii [this message]
2005-05-02 19:56 ` Christopher Faylor
2005-04-29 16:48 ` Daniel Jacobowitz
2005-04-29 17:33 ` Christopher Faylor
2005-04-29 17:58 ` Daniel Jacobowitz
2005-04-29 19:08 ` Christopher Faylor
2005-04-29 19:36 ` Daniel Jacobowitz
2005-04-29 22:01 ` Christopher Faylor
2005-05-02 15:41 ` Andrew Cagney
2005-05-02 15:45 ` Daniel Jacobowitz
2005-04-29 16:04 ` Kris Warkentin
2005-04-29 16:23 ` Mark Mitchell
2005-04-29 16:46 ` Christopher Faylor
2005-04-29 16:50 ` Mark Mitchell
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='01c54f49$Blat.v2.4$609aece0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gdb@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