Announcement

Collapse
No announcement yet.

Some questions about, MESS

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Some questions about, MESS

    Hey again. I have a couple of questions regarding, Mess.

    1: How do you make a trace file? I haven't seen this option anywhere?

    2: How do you properly set a breakpoint? I have tried several times to set a break point, but it never works...

    Any help is appreciated as always. Thanks in return.
    I'm retired from code hacking.
    I do not take requests!

  • #2
    1. trace filename.txt. To stop tracing, use trace off.
    2.
    Code:
    wp address, 1, w   @Breakpoint Write
    wp address, 1, r   @Breakpoint Read
    wp address, 1, rw  @Breakpoint Read/Write
    I think bp address sets a breakpoint on execution.
    I only bother with things that interest me.

    Comment


    • #3
      Mess is a great tool for hacking and there is a little learning curve but once you get used to it it's easy.

      To set a breakpoint on a RAM address you need to use the Watchpoint command wp so here is an example of such a breakpoint:

      wp FF2702,1,w < the 1 is for how many bytes but I've never used anything else and the w is for break on write

      wp FF2702,1,r < this is for a break on read


      a breakpoint on an ASM instruction or as it's known in other debuggers a break on execute is the Breakpoint command bp, example:

      bp 004378

      now to clear the breakpoints or watchpoints use wpclear or bpclear to delete all breakpoints, you can also use bpdisable# or wpdisable# to disable a specific breakpoint and bpenable# and wpenable# to enable that breakpoint. The # corresponds to the breakpoint number when you add a breakpoint.

      Trace logs are made using the command:
      trace filename.log (filename can me be whatever you want)
      traceoff (turns off the trace)


      One of the best features in MESS debugger is the option to ignore breakpoint addresses that keep breaking:

      If you want to watch writes on 21ff but ignore the writes that performed by the code at 7d4 (and so it would normally break at 7d7) then type this:-

      wp 21ff,1,w,pc!=7d7

      you can gang lots of writes to ignore by simplying using &&
      wp 21ff,1,w,pc!=7d7 && pc!=990 && pc!=aa0

      and of course you can add other conditions so that it only breaks when certain values or a ranges of values are poked

      wp 21ff,1,w,pc!=7d7 && pc!=990 && pc!=aa0 && wpdata>2 && wpdata<6




      some useful info and commands:
      http://www.ballyalley.com/ml/ml_tools/MESS_Debugger.txt
      Spoiler Alert! Click to view...

      THE BAD GUY!!!!!!

      Comment


      • #4
        Where on earth do I type this?
        I'm retired from code hacking.
        I do not take requests!

        Comment


        • #5
          I only bother with things that interest me.

          Comment


          • #6
            You have to enable the debugger on the system your playing.
            Spoiler Alert! Click to view...

            THE BAD GUY!!!!!!

            Comment


            • #7
              I can't freaking believe I never saw that little bar down there. >.<
              Thanks guys, it works.
              Last edited by Dybbles; 02-10-2015, 08:47:47 AM.
              I'm retired from code hacking.
              I do not take requests!

              Comment

              Working...
              X