Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Christopher Faylor <me@cgf.cx>
Cc: paul@codesourcery.com,  gdb@sourceware.org
Subject: Re: Windows support in GDB
Date: Fri, 29 Apr 2005 17:05:00 -0000	[thread overview]
Message-ID: <42726830.8070502@codesourcery.com> (raw)
In-Reply-To: <20050429165148.GD12864@trixie.casa.cgf.cx>

Christopher Faylor wrote:
> On Fri, Apr 29, 2005 at 09:43:35AM -0700, Mark Mitchell wrote:
> 
>>Christopher Faylor wrote:
>>
>>>However, now that the patches are finally here, I have to say that I
>>>sort of share Mark K's concerns.  I'm wondering if we are on a slippery
>>>slope and (to mix a metaphor) will be subjecting gdb to a
>>>death-by-inches as we slowly add ifdefs throughout the configury and
>>>code.
>>
>>I think it's a funny time to get concerned -- we're done.
> 
> 
> For now.  Didn't you just theorize more involvement from the MinGW
> community now that your patch is in?

Possibly -- but I'd expect that to be more in the area of adding 
features for debugging Windows applications, if that were to be needed.

> I guess the failure mode will be roughly similar to DJGPP.  Every time
> someone decides that it would be nice to use signal(), select(), fifos,
> inodes, unix-domain sockets, or some other non-msdos construct there
> will have to be a discussion about how to make things work.  But, I
> guess we'd already be having this discussion to with DJGPP so maybe it
> won't be a big deal.

I agree with both your assessment of the potential problem and the 
impact.  (Even Cygwin doesn't provide complete emulation for absolutely 
everything, so I'd imagine that some of that discussion would need to be 
had anyhow.)

>>I certainly don't think the entire codebase will be littered with 
>>HANDLEs and ReadFileEx, or transformed into a multi-threaded application 
>>with a Windows event loop in the middle of it, or anything like that.
> 
> No, but maybe we should rewrite gdb in c++.  That sounds like it would
> solve everything.  :-)

Then Windows support would just be a specialization of some class 
template. :-)

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304


  reply	other threads:[~2005-04-29 17:00 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 [this message]
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
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=42726830.8070502@codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=gdb@sourceware.org \
    --cc=me@cgf.cx \
    --cc=paul@codesourcery.com \
    /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