Page 1 of 1
Bug? POLink error
Posted: Mon Jul 02, 2018 5:52 pm
by kpeters58
Debug Val("A")
results in:
Does anyone see the same (using current beta)?
Re: Bug? POLink error
Posted: Mon Jul 02, 2018 10:09 pm
by Dude
Doesn't happen here. What happens if your anti-virus software is disabled? Maybe that's the cause.
Re: Bug? POLink error
Posted: Tue Jul 03, 2018 1:13 am
by kpeters58
Hmmm - had studied the event logs and found nothing. But disabling Windows Defender SmartScreen changes the behaviour...
Re: Bug? POLink error
Posted: Tue Jul 03, 2018 8:41 pm
by ccode
Hello!
That's 100 percent an antivirus problem.
Are you using a pre-release version of Windows?
Re: Bug? POLink error
Posted: Wed Jul 04, 2018 6:14 am
by Bisonte
ccode wrote:Hello!
That's 100 percent an antivirus problem.
Are you using a pre-release version of Windows?
It's not only a pre-release problem... I saw this with the current 1803 Release also...
sometimes. M$ made the defender more aggressive at the last patchdays...
Re: Bug? POLink error
Posted: Wed Jul 04, 2018 5:54 pm
by kpeters58
Not a pre-release version. But there could be some truth to the last patch day suspicion, as this only started happening very recently...
Re: Bug? POLink error
Posted: Sat Jul 07, 2018 6:59 pm
by troff
same problem, regular updated windows 10
crashes (beta version) when trying to resolve symbols from a dll. old version works fine
Re: Bug? POLink error
Posted: Sat Jul 07, 2018 7:41 pm
by Dreamland Fantasy
I used to get similar messages when using Purebasic with BitDefender running in the background. I ended up having to whitelist the main PureBasic directories and the Windows temporary folder (default place for the compiled programs to be run from) during on access scanning. I haven't had an issue since doing this.
Kind regards,
Francis
Re: Bug? POLink error
Posted: Sat Jul 07, 2018 7:46 pm
by troff
hey all, i am sorry - this was my bad. i used the x86 compiler on a 64 bit dll.
sorry no mistake of the compiler.
Re: Bug? POLink error
Posted: Sun Jul 08, 2018 1:07 am
by Dude
troff wrote:this was my bad
Not entirely - the compiler error message gave zero clues as to what the problem was.