×

Loading...
Ad by
  • 推荐 OXIO 加拿大高速网络,最低月费仅$40. 使用推荐码 RCR37MB 可获得一个月的免费服务
Ad by
  • 推荐 OXIO 加拿大高速网络,最低月费仅$40. 使用推荐码 RCR37MB 可获得一个月的免费服务

I have the third part of your doc. I cannot find what I need in that doc. Anyway Thanks.

I am using a very old linker named xlink386. It links OMF .obj files and generate a .omf file when -OMF option was provided. Another tool prom386.exe generates .bin files from the .omf file. I know that there are public symbols and type information stored in .omf file. I want to analyze the contents of the .omf file and display the memory address of public variables and their values like what a debugger is doing. Anyone can help?

Note: the .obj files are in linkable OMF format. (first byte is 0x80). The .omf file is NOT in ELF format (for ELF, the first 4 bytes must be 0x7F, 'E', 'L', 'F'). I list the first 48 bytes below:
B2 F8 68 60 00 30 37 2F 31 33 2F 30 35 31 34 3A | ..h`.07/13/0514:
32 32 3A 35 36 28 53 53 49 20 4C 49 4E 4B 45 52 |22:56(SSI LINKER
20 26 20 42 55 49 4C 44 45 52 2C 20 56 31 2E 34 | & BUILDER, V1.4
Report

Replies, comments and Discussions:

  • 工作学习 / 专业技术讨论 / Anybody have "Intel OMF specification"? especially I need to know the format of bootloadable file.
    I found a specification that only introduced format of linkable file but no loadable file, bootloadable file and library file. If you have such specification, would you please let me have a look? Thank you.
    • is URL the file you already found? Anyway, isn't OMF object file format? the loadable should be generated by Link tools or lib tools.
      • I have the third part of your doc. I cannot find what I need in that doc. Anyway Thanks.
        I am using a very old linker named xlink386. It links OMF .obj files and generate a .omf file when -OMF option was provided. Another tool prom386.exe generates .bin files from the .omf file. I know that there are public symbols and type information stored in .omf file. I want to analyze the contents of the .omf file and display the memory address of public variables and their values like what a debugger is doing. Anyone can help?

        Note: the .obj files are in linkable OMF format. (first byte is 0x80). The .omf file is NOT in ELF format (for ELF, the first 4 bytes must be 0x7F, 'E', 'L', 'F'). I list the first 48 bytes below:
        B2 F8 68 60 00 30 37 2F 31 33 2F 30 35 31 34 3A | ..h`.07/13/0514:
        32 32 3A 35 36 28 53 53 49 20 4C 49 4E 4B 45 52 |22:56(SSI LINKER
        20 26 20 42 55 49 4C 44 45 52 2C 20 56 31 2E 34 | & BUILDER, V1.4