Software discussion

Web software | www.agner.org

 
thread OBJCONV updated - dos386 - 2013-06-24
last replythread OBJCONV updated - Agner - 2013-06-25
last replythread OBJCONV updated - DOS386 - 2013-08-10
last reply OBJCONV updated - Agner - 2013-08-11
 
OBJCONV updated
Author: dos386 Date: 2013-06-24 14:09
Hi

I see OBJCONV updated. But what's new?

Compared TFM: added support for Knights Rider 512-bit instructions

Are there other differences? I'll compare the source too ...

Problems / wishlist:

- Fix disassembly (got crashes in the past, not sure whether they persist in latest version)

- Progress indicator for disassembly and document "worse than quadratic" (or make it faster) (we had discussed this some time ago)

- Disassemble DGJPP COFF (in my last test with raw COFF I got the code section "nonexecutable" and 1'000'000'000'000 DB's, not a single instruction, if the COFF has MZ stub, it says "16-bit DOS executable, can't disassemble")

- Disassemble raw (and DOS MZ) 16-bit and 32-bit (you already can disassemble PE and (sometimes) localize "local functions" ... there will be no exports and imports in raw)

- Add support for disassembly hint file (telling the disassembler what is code and what not, where to sync, ...) (TFM says that OBJCONV is NOT interactive ...)

- "-ffasm"

   
OBJCONV updated
Author: Agner Date: 2013-06-25 13:58
dos386 wrote:
I see OBJCONV updated. But what's new?
Bug fixes and new instructions.

The slow disassembly of big files is due to an ordered list of symbols. It needs to be replaced by a binary tree. I would rather improve the speed than making a progress meter. Also, I would rather improve the ability to detect what is code and what is data than adding a complicated interactive feature for letting the user do this.

Support for disassembling 16-bit DOS executables is problematic because the code often contains calculated segment addresses, functions implemented as interrupts with parameters mixed into the code and other difficulties. A disassembler needs to be aware of such compiler specific oddities. I suggest that you find an old DOS disassembler.

   
OBJCONV updated
Author: DOS386 Date: 2013-08-10 17:06
Hi

thanks for the answer ... I see that 2.19 is out :-) why not reveal the version number (besides date, bloat, and maybe MD5 or SHA256) on the download page ?

www.agner.org/optimize/#objconv

One more issue: in my DLL it doesn't find any exports or imports:

[link removed]

I'm NOT asking for some horrible interactivity (get IDA PROOOO), but for some simple hint file like

1000 c 100B d 1011 cf 1055 d 1070 n 1400 c

"100B" RVA in hex
"c" code
"d" data
"cf" code and function begin
"n" nothing (skip from disassembling)

what about "-ffasm" ?

   
OBJCONV updated
Author: Agner Date: 2013-08-11 05:59
It's open source. Feel free to add your own features.
It can't disassemble your code properly because it can't trace the self-relative calculated addresses.