LiveCode Forums.

I've had a problem (well, an inconvenience) when compiling
my programmes when Avast Antivirus block the compile
suggesting that my stack contains a nasty of some sort.

I usually get around this by putting the .exe filename on
the exceptions list but the last time this happened I had
to turn Avast off to get the compile to complete. Then
when it came on again it popped up to say that it
was sending my file to their labs for further
investigation.

Worse was to come - users reported my programme
causing their (different) AV throwing an alert when
they tried to run it.

LC 7.1.2 "bog standard" i.e. no externals -- nothing
but out-of-the-book LC code.

Anyone else had this problem?

Happens now and then.

Short answer: send your app to the AV vendor to ask them to review and white list it.

Long answer with some possibly helpful background on how this happens and how good AV vendors make it easy to resolve it:
http://forums.livecode.com/viewtopic.php?f=9&t=26873

Thanks Richard. Pleased to find that it's not
me. At last something for which I can
disclaim any responsibility.

Well, it still might be you. But chances are it's just a false-positive. Does updating Avast resolved it?

FourthWorld wrote:Well, it still might be you. But chances are it's just a false-positive. Does updating Avast resolved it?

As soon as I read your comment it struck me that there
was an update after the problem last appeared and since
then I've compiled a couple of programmes without Avast
getting all agitated. I even checked that protection had
come on after the ten-minute break I gave it.

Another problem solved it seems.

Hi.

In such cases (virus alarm) it's often helpful to double-check the supposed culprit at VirusTotal. Some AV companies are notorious for being rather lazy evaluating their rules ...

And in cases of false alarm, discussing it with the company usually helps quite quickly.

Have fun!