bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/196] objdump fails to read a .sys file


From: nickc at redhat dot com
Subject: [Bug binutils/196] objdump fails to read a .sys file
Date: 10 Jun 2004 14:53:20 -0000

------- Additional Comments From nickc at redhat dot com  2004-06-10 14:53 
-------
Subject: Re:  objdump fails to read a .sys file

Hi James,

> I prefer the following suggested solution:

> 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.

Please try out the attached patch and let me know if it works for you.

Cheers
   Nick

bfd/ChangeLog
2004-06-10  Nick Clifton  <address@hidden>

        * coffcode.h (styp_to_sec_flags): Ignore IMAGE_SCN_MEM_NOT_PAGED
        flags.



Index: bfd/coffcode.h
===================================================================
RCS file: /cvs/src/src/bfd/coffcode.h,v
retrieving revision 1.105
diff -c -3 -p -r1.105 coffcode.h
*** bfd/coffcode.h      17 May 2004 16:40:00 -0000      1.105
--- bfd/coffcode.h      10 Jun 2004 14:51:17 -0000
*************** styp_to_sec_flags (abfd, hdr, name, sect
*** 1063,1069 ****
--- 1063,1077 ----
          unhandled = "IMAGE_SCN_MEM_NOT_CACHED";
          break;
        case IMAGE_SCN_MEM_NOT_PAGED:
+ #if 0
          unhandled = "IMAGE_SCN_MEM_NOT_PAGED";
+ #else
+         /* Generate a warning message rather using the 'unhandled'
+            variable as this will allow some .sys files generate by
+            other toolchains to be processed.  See bugzilla issue 196.  */
+         _bfd_error_handler (_("%s: Warning: Ignoring section flag 
IMAGE_SCN_MEM_NOT_PAGED in section %s"),
+            bfd_archive_filename (abfd), name);
+ #endif
          break;
        case IMAGE_SCN_MEM_EXECUTE:
          sec_flags |= SEC_CODE;


-- 


http://sources.redhat.com/bugzilla/show_bug.cgi?id=196

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]