WardowFujita

AutoIt Project Suggestion, Interactive Debugging Interface

3 posts in this topic

Hello,

To make debugging and fixing of bugs and issues in AutoIt scripts easier, it is a very great idea to add a mode to the AutoIt3.exe Tool that makes one able to step on every lines of code and check contents of variables by their names at one given pause in the execution of the script, or whatever AutoIt native way of handling the script execution such as stack views.

 

The idea;

Place breakpoint on code line, simple and conditional breakpoint that will get triggered only if the specified conditions are met

 

I would see an interface being done with a named pipe/socket, and the interactive debugging being made with an external tool that would connect to the unique pipe corresponding to one AutoIt3.exe instance.

The tool could be third party, but we need an interface to work with.

 

Thank you

Share this post


Link to post
Share on other sites




NEW:     ADO.au3 UDF     POP3.au3 UDF     XML.au3 UDF    How to use IE.au3  UDF with  AutoIt v3.3.14.x  for other useful stuff click the following button:

Spoiler

Last update: 2016-11-12
Any of my own code posted anywhere on the forum is available for use by others without any restriction of any kind. 

My contribution (my own projects): * Debenu Quick PDF Library - UDF * Debenu PDF Viewer SDK - UDF * Acrobat Reader - ActiveX Viewer * UDF for PDFCreator v1.x.x * XZip - UDF * AppCompatFlags UDF * CrowdinAPI UDF * _WinMergeCompare2Files() * _JavaExceptionAdd() * _IsBeta() * Writing DPI Awareness App - workaround * _AutoIt_RequiredVersion() * Chilkatsoft Components * TeamViewer API -UDF * JavaManagement UDF * VIES over SOAPPOP3.au3 UDF *  RTF Printer - UDF * XML.au3 - BETA * ADO.au3 UDF SMTP Mailer UDF * WinSCP UDF *

My contribution to others projects: * _sql.au3 UDF  *

Useful links: * Forum Rules * Forum etiquette *  Forum Information and FAQs * How to post code on the forum * AutoIt Online Documentation * AutoIt Online Beta Documentation * SciTE4AutoIt3 getting started * Convert text blocks to AutoIt code * Games made in Autoit * Programming related sites * Polish AutoIt Tutorial * DllCall Code Generator * 

Wiki: Expand your knowledge - AutoIt Wiki * Collection of User Defined Functions * How to use HelpFile * Best coding practices * 

IE Related:  * How to use IE.au3  UDF with  AutoIt v3.3.14.x * Why isn't Autoit able to click a Javascript Dialog? * Clicking javascript button with no ID * IE document >> save as MHT file * IETab Switcher (by LarsJ ) * HTML Entities *

I encourage you to read: * Global Vars * Best Coding Practices * Please explain code used in Help file for several File functions * OOP-like approach in AutoIt * UDF-Spec Questions *  EXAMPLE: How To Catch ConsoleWrite() output to a file or to CMD *

"Homo sum; humani nil a me alienum puto" - Publius Terentius Afer
"Program are meant to be read by humans and only incidentally for computers and execute" - Donald Knuth, The Art of Computer Programming
:naughty:  :ranting:, be  :) and       \\//_.

Anticipating Errors :  "Any program that accepts data from a user must include code to validate that data before sending it to the data store. You cannot rely on the data store, ...., or even your programming language to notify you of problems. You must check every byte entered by your users, making sure that data is the correct type for its field and that required fields are not empty."

 

Share this post


Link to post
Share on other sites
21 minutes ago, mLipok said:

Debugging applications in such ways is what I have been doing and other people too, homever this way of debugging scripts is very unconfortable when working with big and complex scripts, the issue is not to solve the error, the issue is to find the error, interactive debugging will help a lot in finding an error and provide an overview of it to make the solving easier, the way this page is describing requires one to; while working on an AutoIt program, constantly write code to output every variables contents at every given time and conditions in the script; that is; to achive something such as interactive debugging, there is still the part of stepping inside of code that is missing.

As an example, the way Microsoft does to the .NET Executables, and same thing with C/C++ in Visual Studio, stepping in while being able to view variables content and exact line of code that is executing.

And back to the point of the methods described by the page you're linking, there is a big difference with the possibilities you have when making it internal of the AutoIt system, then with a script written in AutoIt itself.

 

Some quick example to confirm this point;

What if I wanted to skip execution of a line and start execution somewhere else; such as changing the EIP(as an AutoIt equivalent) register?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now