It seems that AVG is accumulating information of the behaviour of programs.
History of Detection:
"Erkennungsname";"Ergebnis";"Erkennungszeit";"Objekttyp";"Prozess"
"Unbekannt, D:\372.dev\megaglest.exe";"Gesichert";"20.01.2013, 10:02:53";"Datei oder Verzeichnis";""
"Unbekannt, D:\372.dev\megaglest.exe";"Gesichert";"22.01.2013, 11:55:28";"Datei oder Verzeichnis";""
"Unbekannt, D:\372dev\megaglest.exe";"Gesichert";"22.01.2013, 13:22:07";"Datei oder Verzeichnis";""
"Unbekannt, D:\372dev\megaglest.exe";"Gesichert";"23.01.2013, 00:02:15";"Datei oder Verzeichnis";""
"Unbekannt, D:\372dev\megaglest.exe";"Gesichert";"01.02.2013, 10:15:49";"Datei oder Verzeichnis";""
since even the releasecandidates of megaglest do not provide any information about its version in filename or comments in the code showed in windows so called "properties" its hard for me to decide which of the daily changing dev-releases I did run. Espacially as I missed the actual detection as a virus for weeks and was wondering how sometimes some file seem to dissappear. But I was not wondering tooo much because I am runng about 8 instances of megaglest in the house and think its possible to get confused managing the daily update of the last new nightly build on different machines.
At last it was the relasecandidate 3.7.1.
megaglest v3.7.1 Compiled using: VC++: 1600 on: Nov 23 2012 00:38:33 platform: Windows endianness
: little
SVN: [Rev: 3948] - using STREFLOP [SSE] - [no-denormals]
which was busted. Mostly it were the dev-versions which were detected, propably because they were called by batch on my system.
The AVG is wide configurable to ignore positiv falses by the user. AVG is not telling too much about the methods of detections of course.
They suggest, the user shall report false positives to them so they will analyze the application and manage their next update.
I think its not worth the time to bother them with development versions.
But anyway, may be its a good idea to put an version info more easy accessable to the file somehow.
Greets