public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@capflow.com>
To: binutils-return-16948-laurent.pinchart=capflow.com@sources.redhat.com
Cc: Laurent Pinchart <laurent.pinchart@skynet.be>,
	 binutils@sources.redhat.com
Subject: Re: binutils & Windows device drivers
Date: Tue, 09 Apr 2002 05:13:00 -0000	[thread overview]
Message-ID: <3CB2DB4E.60505@capflow.com> (raw)
In-Reply-To: <m3n0wdjegt.fsf@north-pole.nickc.cambridge.redhat.com>

>
>
>>>>Could anyone tell me if binutils supports the PE-386 format used by
>>>>Windows device drivers (.sys) ?
>>>>
>>>Sadly, it appears that this format is not supported.
>>>
>>Actually the .sys format seems to be a 'standard' PE-i386. The
>>problem I experienced with the latest CVS binutils was that
>>IMAGE_SCN_MEM_NOT_PAGED was not supported. I removed the check in
>>bfd, and I got objdump to work properly (which was all I needed). Is
>>there an easy way to add support for IMAGE_SCN_MEM_NOT_PAGED without
>>too much changes in BFD ?
>>
>Probably not.  BFD does not currently support the concept of a
>non-paged section.  (It supports non-paged binary object files, where
>all of the sections are not paged, but not on a per-section basis).
>
>Such support could be added of course, but it would involve someone
>doing the work.
>
I unfortunately don't have enough skills to do the work. Would any other 
file format benefit of non-paged sections support ?

>If the only problem you had was bfd barfing on the
>IMAGE_SCN_MEM_NOT_PAGED flag however, then it might well be possible
>to add a switch to change the error message to a warning and allow the
>dump to continue.
>
I just removed the check before compiling libbfd and objdump works fine.

Do you know any other difference between 'standard' PE-i386 files and 
the '.sys' format ?

Laurent Pinchart


  reply	other threads:[~2002-04-09 12:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-26 23:54 Laurent Pinchart
2002-04-09  2:46 ` Nick Clifton
2002-04-09  2:55   ` Laurent Pinchart
2002-04-09  4:31     ` Nick Clifton
2002-04-09  5:13       ` Laurent Pinchart [this message]
2002-04-09  5:42         ` Eric Kohl

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=3CB2DB4E.60505@capflow.com \
    --to=laurent.pinchart@capflow.com \
    --cc=binutils-return-16948-laurent.pinchart=capflow.com@sources.redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=laurent.pinchart@skynet.be \
    /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).