SAD debugger and SmartCrash

[kas1e]

Hi all. I use SmartCrash for replace suspend/reboot window , and have little question about it. All buttons work correctly except 'debug'. Just halt my system. I have aos3.9/bb2. In guide said:

 @{b}Debug@{ub}
      Call the system debugger. By default this debugger
      is "SAD" in >= V39 and "ROM-WACK" in < V39.
 

Well, for me is SAD. But what is it SAD ? Where is placed ? (if in ROM, which address ?). And why system halt ?

btw, i use blizkick from 3.0 to 3.1, maybe here is problem ?

[Piru]

SAD overview

[kas1e]

Woah ! Thanks!

Really nice overwiev ! So, i have question for you Do you have win32 programm for SAD using ?

And yes, it is not halt for me:
-----
If no command is received within <2> seconds, it will emit $BF
again and loop back.  (This is the "heart beat" of SAD)
If SAD does not get a responce after <10> heartbeats, it will return to the system.
------

Well, after 20 second i recieve SmartCrash window agayn and back to system.

[kas1e]

@piru
And some more questions for you what is the best tools for debugging/bugs handler ? As i understand:
SmartCrash + SegTracker - for suspend/reboot window

What about Enforcer and Mungwall ? It can be usable ?