AmigaMance wrote:
Hi.
I have made a small dos script which i execute whenever i want to test a program and report any possible hits to its developer. This script runs the following tools:
SegTracker
MuForce
MuGuardianAngel and
Sashimi to redirect the output of these tools to a console window.
Is this enough or should i add something else to the script?
Are these tools good or are there any better replacements?
SegTracker should be running right after SetPatch -- otherwise it will not find the hunks most common libraries loaded. It does no harm to system performance, so you can also run it without debug sessions.
Sashimi can and should be started first in case something happens right after the start of MuForce or MuGuardianAngel.
MuGuardianAngel already contains the functionality of MungWall, so this is not needed. In my script, I also increase the lines of disassembly and other stuff, but I don't have it right here for posting.
I also really recommend Piru's SmartCrash tool as standard equipment. Laire's Barfly also has a great debugger.
