"Debug tools"

[AmigaMance]

  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?

[Jose]

The most used ones are Enforcer and Mungwall, never tried the ones you listed but maybe they do the same thing ?

[AmigaMance]

I don't know about Mungwall, but the doc of MuForce says that it replaces the old Enforcer.

[AmigaMance]

 Ok, there are no further suggestions about what i asked, so i'm going to assume that the list of tools i'm using is complete and there are no better replacements for them or need for any additional ones. You see, i am a simple user, i have no coding knowledge.

 Btw, does any of you think that my new sig is irritating? Just say so if you do. I can remove it if some members finds it irritating. I don't know.. 2 threads in a row... anyway.

[ChaosLord]

Here is my debug script that I have been using for years.
It is almost the same as yours.  I donno which is better: Sushi or Sashimi?

segtracker
run muforce stdio  DISPC
wait 4
run muguardianangel nametag nostackwarn SHOWHUNK DISPC
wait 3
run sushi asksave

You are the 1st software tester I have met who is interested in a debug script!!!  I have never been able to convince any of the 37 Total Chaos playtesters to use such a script.  You are welcome to test for me anytime.  :-)

[AmigaMance]

From what i read Sashimi is an enhanced Sushi replacement.
Your script is much similar to the one i'm using. Ok..
 I see that you have uploaded a new update of Total chaos on Aminet. I will give it a go when i find time and send you any debug logs from it.

[platon42]

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.

[AmigaMance]

@Platon42
 I see. Thanks :-)

[JosDuchit]

would it be possible to post script used today?
Especially for OS4

[DrCinicus]

Other debug tools:

http://aminet.net/dev/debug/PatchWork.lha

 it's useful to find errors in OS calls

http://aminet.net/dev/debug/CodeWatcher.lha

 to check allocations and releases of OS resources.

 Bye
 Fabio