Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Charles Wilson <cygwin@cwilson.fastmail.fm>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: ensure binary objects opened in binary mode
Date: Fri, 24 Feb 2006 11:44:00 -0000	[thread overview]
Message-ID: <u8xs19h4o.fsf@gnu.org> (raw)
In-Reply-To: <43FEC572.3090403@cwilson.fastmail.fm> (message from Charles 	Wilson on Fri, 24 Feb 2006 03:36:02 -0500)

> Date: Fri, 24 Feb 2006 03:36:02 -0500
> From: Charles Wilson <cygwin@cwilson.fastmail.fm>
> 
> Alrighty then -- here's the next iteration.  Both parts have changed a 
> bit: the first patch no longer removes #include <fcntl.h> from solib.c, 
> while the second patch ONLY addresses the #ifndef O_BINARY clutter and 
> no longer removes <fcntl.h> from the 48 files.
> 
> Patch 1:
>   defs.h  |   12 ++++++++++++
>   solib.c |   12 ++++++------
>   2 files changed, 18 insertions(+), 6 deletions(-)
> 
> 2006-02-24  Charles Wilson  <cygwin@...>
> 
> 	* gdb/defs.h: unconditionally include <fcntl.h>, and
> 	ensure that O_BINARY is defined.
> 	* gdb/solib.c(solib_open): ensure solib files are opened in
> 	binary mode.
> 
> Patch 2:
>   corelow.c    |    3 ---
>   exec.c       |    3 ---
>   remote-rdp.c |    3 ---
>   source.c     |    3 ---
>   symfile.c    |    3 ---
>   5 files changed, 15 deletions(-)
> 
> 2006-02-24  Charles Wilson  <cygwin@...>
> 
> 	* gdb/corelow.c: Remove O_BINARY macro definition.
> 	* gdb/exec.c: Remove O_BINARY macro definition
> 	* gdb/remote-rdp.c: Remove O_BINARY macro definition
> 	* gdb/source.c: Remove O_BINARY macro definition
> 	* gdb/symfile.c: Remove O_BINARY macro definition
> 
> Per cgf's earlier message, I can go ahead and check this in myself 
> assuming everybody's happy with it at this point?

I'm certainly happy.  Thanks!


  reply	other threads:[~2006-02-24 10:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-17 22:02 Charles Wilson
2006-02-17 23:41 ` Christopher Faylor
2006-02-18 10:45   ` Eli Zaretskii
2006-02-18 11:19     ` Mark Kettenis
2006-02-18 11:47       ` Eli Zaretskii
2006-02-18 11:55         ` Mark Kettenis
2006-02-22  5:52         ` Charles Wilson
2006-02-22 17:06           ` Christopher Faylor
2006-02-22 18:50           ` Eli Zaretskii
2006-02-22 21:55             ` Daniel Jacobowitz
2006-02-24 10:37               ` Charles Wilson
2006-02-24 11:44                 ` Eli Zaretskii [this message]
2006-02-25  7:29                   ` Charles Wilson
2006-03-01 22:11             ` Michael Snyder
2006-02-18 10:50 ` Eli Zaretskii

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=u8xs19h4o.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cygwin@cwilson.fastmail.fm \
    --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