Jump to content
Mbee

Solved [Curious Error trying to use AutoIt Debugger]

Recommended Posts

Mbee

I've never seen this error before using the AutoIt graphical debugger, but nothing I've tried everything I can think of.

I've tried asking at FoolOnTheHill, the English language forum for this debugger, but apparently it's been dead for years.  And although it's possible the author's German language support forum is still running, I can't read or write German, and I can't find anywhere else to get support.

What's happening is that I first set a breakpoint early on, and then when I press "Run", I'm now always getting the following error:

Line 600 (File "C:\MyScripts\MyScript\Debug\MyScript.DebugScipt.au3");

#include "C:\MyScripts\MyScript\Debug\MyScript.DebugScipt.au3"

Error: Error opening the file.

Now, I've checked carefully, and everything in the Debug folder looks fine!  Nothing's set to read-only, nothing's hidden, and I can open all the files there just fine as well.

I thought maybe my damn antivirus was getting in my way again, but I disabled it and the problem remains.  I've also tried deleting the Debug folder and letting the debugger create it from scratch, but that doesn't solve it either.

I'm desperate for help, please!?

Thanks!

Edited by Mbee

Share this post


Link to post
Share on other sites
VIP

File "C:\MyScripts\MyScript\Debug\MyScript.DebugScipt.au3" does not exist or an other program  open/use it!


Regards,
 

Share this post


Link to post
Share on other sites
Mbee

Thanks for your swift reply, Trong!  But none of those things is the case.

First, the appropriate files in the Debug folder DO exist.

And to insure that nothing was opened in any other app, I completely shut down and restarted, and when it was finished booting, the first and only thing I did was to right-click on the script and select "Debug".

I got the exact same error.

Any other suggestions, please?

Share this post


Link to post
Share on other sites
VIP

Line 600 is #include "C:\MyScripts\MyScript\Debug\MyScript.DebugScipt.au3" ?

 If not, post that line on here!


What is your script name, and it is located in "C:\MyScripts\MyScript\Debug\" ?


Regards,
 

Share this post


Link to post
Share on other sites
Mbee

Ah! I semi-solved it!

All I know is that when I disabled the "Debug user-supplied local "include" files" in the Debugger Options, the problem went away.

I'm not sure why that was such a bad thing, but it's working now and that's all I needed.

Thanks again for your kind replies!

 

 

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

  • Similar Content

    • valdemar1977
      By valdemar1977
      Dbug is graphical debugger for AutoIt.
      Project started by @Heron in 2009 and now supported by @asdf8 and @valdemar1977.
      Features
      Debug the complete script or just parts of it Display run status (line number of currently executed function) GUI default always-on-top in the upper right corner for comfortable debugging WM_NOTIFY and WM_COMMAND hook to prevent interference with possible message handlers Display scope, type and value of variables, expressions, macro's and constants (global AND function local) Execute commands in an immediate window. Can be expressions, functions and assignments Detailed display of array, struct and object variables Dynamic display of variable value in the source code (under cursor) Array table viewer with ability to view the sub-arrays, the correct handling of macro @Error, @Extended and other changes OEM and ANSI console output Conditional breakpoints Saving settings and debugging state and much more... How to use
      Extract from downloaded archive _Dbug.au3 to your Autoit include dir Add #include <_Dbug.au3> in to your code and run code Before compile or buid comment or remove #include <_Dbug.au3> from your code
×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.