Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] win32-nat.c: Simplify generation of Windows environment
Date: Sat, 09 Dec 2006 08:01:00 -0000	[thread overview]
Message-ID: <m364cljy4w.fsf@codesourcery.com> (raw)
In-Reply-To: <upsauvo6f.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 08 Dec 2006 09:31:36 +0200")


Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: gdb-patches@sourceware.org
>> From: Jim Blandy <jimb@codesourcery.com>
>> Date: Thu, 07 Dec 2006 16:10:14 -0800
>> 
>> $ cd gdb/config
>> $ grep -nH -e win32-nat */*.m? 
>> i386/cygwin.mh:2:NATDEPFILES= i386-nat.o win32-nat.o corelow.o
>> $ 
>> 
>> I think that means it's just Cygwin.
>
> No, it just means that the native W32 build is currently not part of
> the CVS.
>
> A large portion of win32-nat.c is relevant to any native Windows
> debugger.  By contrast, cygwin_internal is obviously Cygwin-specific.
> So I think it would be a good practice to mark such specific portions
> of code explicitly.

Given what I've read so far, I don't agree.  In general, for the
intents and purposes of the Project GNU debugger, win32-nat.c is
Cygwin-specific.  If someone is maintaining out-of-tree W32 patches,
then it is up to them to amend those patches to add the sort of
#ifdefs you suggest.  It's not reasonable to expect contributors to
the the public GDB sources to anticipate and accomodate the needs of
code they can't see.

But that's "in general".  If there's a further story here that can be
told where some minor effort on our part will make it easier for
someone to participate and contribute to GDB, then I think folks here
are pretty friendly and would be willing to listen.


  parent reply	other threads:[~2006-12-09  8:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07  9:58 Corinna Vinschen
2006-12-07 16:35 ` Corinna Vinschen
2006-12-07 19:48 ` Jim Blandy
2006-12-08  8:57   ` Corinna Vinschen
2006-12-07 21:37 ` Eli Zaretskii
2006-12-08  0:09   ` Jim Blandy
2006-12-08  7:31     ` Eli Zaretskii
2006-12-08  9:12       ` Corinna Vinschen
2006-12-08 11:31         ` Eli Zaretskii
2006-12-08 12:05           ` Corinna Vinschen
2006-12-09  8:01       ` Jim Blandy [this message]
2006-12-08 20:43   ` Christopher Faylor
2006-12-09  9:15     ` Corinna Vinschen

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=m364cljy4w.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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