short: MorphOS hit interceptor
uploader: dev blubbedev net
author: Leif Salomonsson
type: dev/e
version: June 2011
architecture: ppc-morphos = 1.4.5

   What ?

      It intercepts powerpc hits on morphos and tries to give some
      additional information, information it gathers from debug data
      that ecx puts in executables if you compile with vardebug/s.
      It does this fully automatically, no need to execute special
      tools on commandline or such.

   The Amazing Features:

      o Shows SYMBOL information (Any PPC ELF with symbols required)

      o Shows SOURCE, LINE information (ECX PPC ELF required)

      o Shows a PPC disassembly around hit offset.

      o Shows variable dump. (ECX PPC ELF required)

      o Works on libraries/devices too.
        Process.PROGDIR:, Process.PROGDIR:Libs/, 
        Process.PROGDIR:Devs/, LIBS:, DEVS: is searched.
        (Any PPC ELF required)

      o PPC register dump, stack backtrace, frame dump.

      o 68K register dump, stack backtrace, frame dump.
        If hit occured under emulation, also quick 
        registers/trace/dump is done.

      o Is almost guaranteed to not steal you beer and send them to author.


   Usage:

      CatchHit TARGET/A, DISLEV/N, EATMSG/S, BTDEPTH/N, DUMPLINES/N

      TARGET/A   
			
			- Name of running task, or "global" for all tasks.

      DISLEV/N   
			
			- # of lines of additional disassembly around hit, default is 0 (=just one instruction).

      EATMSG/S   
			
			- Do not send trap message to logserver. Will shut logserver up.

      BTDEPTH/N  
			
			- Stack backtrace depth. Defaults to 1.

		DUMPLINES/N 
			
			- # of lines to dump around frames. Defaults to 4. 

   Requires:

      Something that intercepts debug output, because CatchHit sends
      it's output with DebugF(). I'd recommend using Sashimi.
      Otherwise ramdebug or serial output is used.

   Other:

      Exit is possible by sending ctrl c.

      If you find what might be a bug, please report.
      
      This tool is not particulary beginner friendly, but
      rather verbose and aimed at the experienced coder who
      knows what stuff like "SRR0" means and who finds memory
      dumps around the stack interesting and so on.


	History:
	
		December 2010
		-------------
		
		o Initial release.
			
		June 2011
		---------
		
		o Various fixes, improvements, additions.