From: Ian Lance Taylor <ian@zembu.com>
To: khan@xraylith.wisc.EDU
Cc: ts1@cma.co.jp, binutils@sourceware.cygnus.com
Subject: Re: patch for i386-pe section header [Re: section bug?]
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <19990627012422.14497.qmail@daffy.airs.com> (raw)
In-Reply-To: <199906262331.SAA01315@mercury.xraylith.wisc.edu>
Date: Sat, 26 Jun 1999 18:31:14 -0500
From: Mumit Khan <khan@xraylith.wisc.EDU>
The following should fix this bug.
Sat Jun 26 18:25:30 1999 Mumit Khan <khan@xraylith.wisc.edu>
* peicode.h (coff_swap_scnhdr_out): Mark user-defined writable
sections as writable.
Index: bfd/peicode.h
===================================================================
RCS file: /cvs/binutils/binutils/bfd/peicode.h,v
retrieving revision 1.3
diff -u -3 -p -r1.3 peicode.h
--- bfd/peicode.h 1999/05/25 11:37:40 1.3
+++ bfd/peicode.h 1999/06/26 23:22:14
@@ -1234,6 +1234,8 @@ coff_swap_scnhdr_out (abfd, in, out)
| IMAGE_SCN_MEM_SHARED | IMAGE_SCN_MEM_READ);
else if (strcmp (scnhdr_int->s_name, ".rsrc") == 0)
flags |= IMAGE_SCN_MEM_READ | IMAGE_SCN_MEM_SHARED;
+ else if (! (flags & SEC_READONLY))
+ flags |= IMAGE_SCN_MEM_WRITE;
else
flags |= IMAGE_SCN_MEM_READ;
In the second new line, shouldn't that be
flags |= IMAGE_SCN_MEM_READ | IMAGE_SCN_MEM_WRITE
?
I would almost just check that in, but I thought I'd better check to
see if I was missing something.
Ian
next prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 section bug? SONE Takeshi
1999-07-01 0:00 ` patch for i386-pe section header [Re: section bug?] Mumit Khan
1999-07-01 0:00 ` Ian Lance Taylor [this message]
1999-07-01 0:00 ` Mumit Khan
1999-07-01 0:00 ` Mumit Khan
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=19990627012422.14497.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=binutils@sourceware.cygnus.com \
--cc=khan@xraylith.wisc.EDU \
--cc=ts1@cma.co.jp \
/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).