MHS Debugger vs WarCraft 3 The Frozen Throne.

[L. Spiro]

On the error report.

They changed it on Windows Vista to make it gay so you don’t know anything about why it crashed.


Anyway, if your problem is related to actually debugging, not just disassembling, it means the target process is writing to the RAM of MHS to spoil its code and make it crash. It makes it seem as if it is MHS’s fault and it gets rid of the debugger.


L. Spiro

[WhiteHat]

On the error report.

Then i did write it in my previous post. Only a few though...

The Technical Error Information > Error Report Contents has really a lot of
info that i don't think i can write all of it here... >.<

It contains (in summary):
- Exception Information (along with its detailed info)
- System Information (along with its detailed info)
- Module 1 (along with its detailed info)
- Module 2 (along with its detailed info)
- Module 3 (along with its detailed info)
- ...
- Module 52 (along with its detailed info)
- Thread 1 (along with its details, include a hex-editor-like info)
- Thread 2 (along with its details, include a hex-editor-like info)
- Thread 3 (along with its details, include a hex-editor-like info)
- ...
- Thread 8 (along with its details, include a hex-editor-like info)
- Memory Range 1 (along with a hex-editor-like info)
- Memory Range 2 (along with a hex-editor-like info)
- Memory Range 3 (along with a hex-editor-like info)
- ...
- Memory Range 17 (along with a hex-editor-like info)
- Entire Contents (along with a hex-editor-like info)

I hope i don't have to type them all, cause it'll take centuries... >.<
But, maybe, i would post some screen shots of it...

Anyway, if your problem is related to actually debugging, not just disassembling, it means the target process is writing to the RAM of MHS to spoil its code and make it crash. It makes it seem as if it is MHS’s fault and it gets rid of the debugger.

For your information, the crash happened after 2 conditions:
- Upon attaching debugger (Find What Accesses/Writes This Address) in table.
- Open menu : MHS > Tools > Disassembler.

[L. Spiro]

If you find what reads an address it loads the Disassembler anyway which means it may only be one condition.

You can debug without loading the Disassembler by using scripts to start the debugger.


L. Spiro

[WhiteHat]

If you find what reads an address it loads the Disassembler anyway which means it may only be one condition.

So, the crash happens upon loading the Disassembler...

You can debug without loading the Disassembler by using scripts to start the debugger.

Goint to need a while to be able to make the script...

[WhiteHat]

There is a slight difference for MHS 4.0.0.14.

With war3.exe as target process, MHS doesn’t close (with error) whenever i
open the debugger (MHS 4.0.0.13 closes n error immediately). Only, there is
nothing else shown in the debugger window, not even the assembly codes...

MHS 4.0.0.14 closes (followed by error message) immediately if i attached
the debugger to an address from the table. And a few seconds after that, WC3
closes with an error message... Maybe cause the debugger detached improperly.

[L. Spiro]

The Debugger does not detach improperly; their protections are causing all of these problems and their error message is fake.

The Disassembler starts on an invalid address. All you need to do is Ctrl-G and go to a valid address.


L. Spiro

[WhiteHat]

The Debugger does not detach improperly; their protections are causing all of these problems and their error message is fake.

If what you mean by “their protections” was WC3 protection, then i have to
say that i don’t know whether WC3 implement any protection like gameguard...
I am playing Single Player mode only. Not quite interested in multi-player mode.

However, i simply think that there is no any kind of protection since CE 5.3 can
debug WC3 (tho i don’t like to use CE, but i have no choice)... It is a standard
CE and not an ‘undetected’ one...

The Disassembler starts on an invalid address. All you need to do is Ctrl-G and go to a valid address.

I tried that and it worked... But, still can’t debug the game.

[L. Spiro]

You do not need to debug the game to view the Disassembly.


L. Spiro

[WhiteHat]

You do not need to debug the game to view the Disassembly.

LoL ... I know that...

It’s my goal to debug Warcraft 3 TFT with MHS. To see that MHS 4.0.0.14 can
view war3.exe disassembly is a good thing since i can’t do it in MHS 4.0.0.13.

However, it’s not good enough cause i can’t debug war3.exe, which leave me
no choice but to use CheatEngine to debug war3.exe.

Now, if CE is able to debug war3.exe, then why MHS not able to do the same ?
(it’s absolutely no offense. Cause i really want to debug war3.exe with MHS)

Edit:
FINALLY I CAN DEBUG WARCRAFT 3 TFT !!! (sorry for the caps, can’t help it) :p
I just realized that we can Open Process for Debug... LoL ~ OMG ...

Now, the problem is 90%++ solved...

Isn’t this strange ?
If i attach debugger in the middle of the game, MHS crashes. But if i open
war3.exe for debug, it works smooth. It’s good news tho confusing ...