DSO Disassembler
by Tetragrammaton · in Torque 3D Professional · 05/26/2012 (3:03 pm) · 7 replies
Well, I'm currently working on a big project with some friends and is there any sort of DSO Disassembler? If yes, then i would like if someone could post it here, because i read somewhere that a DSO Disassembler exists, but i couldn't find it anywhere. So, if someone finds it, could they post it please here.
Thanks in advance,
Cajetan.
Thanks in advance,
Cajetan.
About the author
#2
05/27/2012 (9:09 am)
Could also be a modding initiative.
#3
05/27/2012 (9:39 am)
I also *think* that decompiling a DSO would only work from within the project/executable it was compiled with.
#4
I have the code to decompile the DSOs, but honestly, i do not feel to distribute.
05/27/2012 (11:41 am)
No Michael... the DSO are serialized in the same way. Your DSO generated from your T3D, work also on my T3D, as long as the two T3D is of the same version. This is a big security problem, resolvable simply.I have the code to decompile the DSOs, but honestly, i do not feel to distribute.
#5
I've seen a couple different DSO decompilers over the years, but also wouldn't distribute it even if I still had it/them.
05/27/2012 (11:55 am)
Quote:That's what I meant actually. I'm very sure that my version of T3D is different from anyone else's. I recall managing to decompile my own scripts generated from my unique version, but the same process failed on other DSOs, so it seemed pretty much project dependent.
Your DSO generated from your T3D, work also on my T3D, as long as the two T3D is of the same version.
I've seen a couple different DSO decompilers over the years, but also wouldn't distribute it even if I still had it/them.
#6
05/27/2012 (3:55 pm)
Michael, I'm sorry, but I'm not here to steal another project. I also didn't called up for a "Decompiler", because as I know, Decompiling a DSO is impossible anyway. You can only Disassemble it. I was asking if there is any Disassembler for DSO files. And if there are, then I please them to post it here.
#7
I am not sure there is much value in doing so. What are you hoping to accomplish? Maybe there is a better way.
Edit:
Are you trying to see what opcodes it creates to for optimizing? That is what an assembler source is used for with C code. That way you can see if the compiler is creating something wonky. Usually with TS to optimize means take slow part and write as C function.
05/27/2012 (11:22 pm)
Cejtan, look at the CompileEval.cc and look for the symbols it parses like OP_CREATE_OBJECT. Find where those are defined and that should give you all the opcodes. From there you may be able to build your own disassembler. Use the opcodes to determine what is what and also dig through the source to determine file structure. The fact is it is all there in the codebase. I am not sure there is much value in doing so. What are you hoping to accomplish? Maybe there is a better way.
Edit:
Are you trying to see what opcodes it creates to for optimizing? That is what an assembler source is used for with C code. That way you can see if the compiler is creating something wonky. Usually with TS to optimize means take slow part and write as C function.
Associate Michael Hall
Distracted...