hey, i know it’s still a beta, but when i try to run avast it says “Segmentation fault”…anyway to work around this?
I know about it and it will be fixed. The cause is, that you haven’t set ‘AVAST4DIR’ and ‘AVAST4TMPDIR’ environment variables…
Could you please explain what, where and how the paths have to be set?
Are there any issues with Kernel 2.6.x?
What Linux distribution are you using?
No, there are no known issues. Actually, this thread was created pretty long time ago (more than a year ago) and was only relevant to the beta version.
At which stage does the program fault? Immediately after running?
Thanks
Vlk
I’m currently running Mandrake 10 (Final).
The kernel version is 2.6.3 (original install kernel).
Amavis/Amavisd both run, but the update causes the fault below:
[root@alex bin]# ./avastvpsreload
Segmentation fault
I haven’t looked into this very deeply, just checked the forum and left a note. Here is info from /var/log/avastvpupdate:
[root@alex log]# cat avastvpsupdate
Sun Sep 12 04:02:01 2004 ----- avastvpsupdate.pl started -----
Sun Sep 12 04:02:01 2004 VPS file changed, downloading latest.
Sun Sep 12 04:02:05 2004 VPS file downloaded.
Sep 12 04:02:05 avastvpsreload[5184]: info: Starting the avast! virus signature database reloader
Sep 12 04:02:06 avastvpsreload[5184]: info: new VPS file moved to ‘/var/lib/avast4/’ directory
Sep 12 04:02:06 avastvpsreload[5184]: info: started update of the new VPS 0437-1 (date: 09.09.2004)
Sun Sep 12 04:02:06 2004 Current VPS version: 0437-1 (date: 09.09.2004)
So according to the log, all is well… what is the best way to check to see if the software has been updated? I haven’t opened any firewall ports (yet) I will do so this am and see if the message changes.
Thank you.
What about the on-demand scanner? (I mean running avast from that command line). Does the work correctly??
Thanks.
The on-demand scanner works perfectly.
The avastvpsreload binary is only used for updating the virus signature database into memory. It seems it works correctly together with your avastvpsupdate.pl script.
Please, run avast! Then execute the avastvpsreload binary from the command-line (see for output) and then run ‘ipcs’ command to see if IDs of shared memory allocated by avast! has changed.
Thank you for all of your help.
When running the perl script “avastupdate.pl”, everything works correctly. I think it was my ignorance that caused this whole problem.
I was trying to execute “avastvpreload” directly, instead of using the script.
I very much appreciate the quick and informative responses.
Thank you,
Alex
Hi there,
I’ve just downloaded avast! 4 for linux and received demo key, but it seems that I also have some problems with segfaults.
Without running the avastupdate.pl script on-demand scanner fails with segmentation fault when trying to scan a file. If I do not try to scan something, it works (prints help)
After that I executed the update script and scanner fails again 
Tryed to execute avastvpspreload by hand, it segfaults too.
All this is on Fedora Core 2 with 2.6.8 kernel.
gdb dump if it will be of help:
[root@avalon viruses]# gdb avast
GNU gdb Red Hat Linux (6.0post-0.20040223.19rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type “show copying” to see the conditions.
There is absolutely no warranty for GDB. Type “show warranty” for details.
This GDB was configured as “i386-redhat-linux-gnu”…(no debugging symbols found)…Using host libthread_db library “/lib/tls/libthread_db.so.1”.
(gdb) set args WinUpdate.*
(gdb) run
Starting program: /usr/bin/avast WinUpdate.*
(no debugging symbols found)…(no debugging symbols found)…(no debugging symbols found)…(no debugging symbols found)…(no debugging symbols found)…[Thread debugging using libthread_db enabled]
[New Thread -151127968 (LWP 18387)]
(no debugging symbols found)…[New Thread 23477168 (LWP 18396)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -151127968 (LWP 18387)]
0x0019c9a6 in avscanRepairEx () from /usr/lib/libavastengine.so
(gdb) bt
#0 0x0019c9a6 in avscanRepairEx () from /usr/lib/libavastengine.so
#1 0x0019c895 in avscanRepairEx () from /usr/lib/libavastengine.so
#2 0x001a1bde in avscanRepairEx () from /usr/lib/libavastengine.so
#3 0x0018f5a2 in ?? () from /usr/lib/libavastengine.so
#4 0x0018f604 in ?? () from /usr/lib/libavastengine.so
#5 0x0018f63e in ?? () from /usr/lib/libavastengine.so
#6 0x00197bcf in avscanScanReal () from /usr/lib/libavastengine.so
#7 0x00190bb1 in avworkCleanup () from /usr/lib/libavastengine.so
#8 0x001909fb in avworkCleanup () from /usr/lib/libavastengine.so
#9 0x00192087 in avworkCleanup () from /usr/lib/libavastengine.so
#10 0x00192938 in avfilesScanReal () from /usr/lib/libavastengine.so
#11 0x0804bf53 in ?? ()
#12 0x08054218 in ?? ()
#13 0xfefffbf1 in ?? ()
#14 0xfeffef98 in ?? ()
#15 0x00000001 in ?? ()
#16 0x00000000 in ?? ()
(gdb)
will be repaired in a next version