Question - Faster way to debug?

[s0lusek]

Hey all,

Any time something goes wrong, the ultimate debug move for me is to start adding echo lines in all over the place to trace the flow of the macros through each function etc. Before I start turning this into a proper debugging function that I can turn off and on, is there something built in to macroquest that can help with this? Or are there other ways of doing this? I'm using notepad++ to do my editing, can you do anything like watch the code execution path and insert break points?

 

[Maskoi]

Use visualstudio 2015 and attach the debugger to it. It will show every line mq2 is running and where it crashes.

 

[s0lusek]

Anyone willing to point me in the direction of some materials on getting started with Visual Studio and macro files for MQ2? I'd love to begin debugging my macros, not sure where to begin.

 

[eqmule]

You can't "exactly" debug macros, there is no editor which let you set breakpoints on actual macrolines (yet).

What maskoi means is you can debug MQ2 and its plugins and set breakpoints in the macroengine etc...

/echo is your best bet when it comes to pinpointing macro problems atm.

 

[Maskoi]

What I mean is you will see the Stream of everything including every macro command running throughin the VS output window. when it crashes you will see the last macro lines that ran before the crash so it gives you a very good idea what code is crashing you if its a macro and not a plugin.

I will write up a quick guide for you when I get home tonight from work.

This is what i do on macros other than Kiss.

Kiss has such extensive debugging built in we don't need to attach a debugger.

 

[s0lusek]

That sounds great, thanks Mask.