Page 1 of 1

New and unsaved file debugging

Posted: Mon Apr 06, 2020 2:12 pm
by JagV12
Hi there,

I'm using PureBasic 5.72 on a W7x64 machine. As a beginner, I take (clipboard text copy) sample programs here and there and paste them in a new tab in my PB 5.72 Editor. Then I hit F5 to debug them but if the program hasn't been saved first (hence given/giving a filename), the compiler/debugger hangs somehow and then issues an obscure warning.

Maybe a "Please save file first" warning would be more appropriate...

// Edit: Moved from "Bugs" to "General Discussion" (Kiffi)

Re: New and unsaved file debugging

Posted: Mon Apr 06, 2020 2:26 pm
by kenmo
Hi,

You need to provide some example code and the error message... because this should work perfectly fine.

I just tested it on 5.72 on Windows 10 and had no problem. It's likely a setup problem, like it's trying to save a temp file to a folder it doesn't have permission to.

Re: New and unsaved file debugging

Posted: Mon Apr 06, 2020 2:28 pm
by mk-soft
This looks more like the virus scanner.
Since the unsaved file is created in the temp folder of the execute, the virus scanner grabs and blocks this file.

Must see how to set the exceptions in the virus scanner.
For me I would use the compiler, linker added to the exceptions

Re: New and unsaved file debugging

Posted: Mon Apr 06, 2020 3:01 pm
by Josh
Please do not post in the bug forum if you are unfamiliar with something.

https://www.purebasic.fr/english/viewto ... f=4&t=4701

Re: New and unsaved file debugging

Posted: Mon Apr 06, 2020 4:14 pm
by JagV12
You' re probably right about the virus scanner. Avast is not very friendly with PureBasic... I'll see what I can do...
Thanks for the support