Debian Lenny Segmentation fault

system · 2008-01-25T18:30:33.000Z

Hi there,

I was glad to see Avast for Linux as my experiences on the other operating system where very satisfying. I’m sorry I cannot say the same for my linux home server. Here I encounter segmentation faults. The error message in question is:

/usr/bin/avastgui: line 169: 23526 Segmentation fault $AVAST_PREFIX/bin/$programname $*

and also

/usr/bin/avast: line 169: 27770 Segmentation fault $AVAST_PREFIX/bin/$programname $*

I’m running on:

Linux siefu 2.6.22-3-686-bigmem #1 SMP Mon Nov 12 09:52:20 UTC 2007 i686 GNU/Linux

Is there some kind of debug switch to get some real debugging info. Just reporting the last line of the wrapper script isn’t very helpfull.

BTW seems that this happens every time it hits on the OLPC qemu image.

I have removed the file in question but now it just stops a few moments later on an other file. It’s always the same file till you remove it. Then another file triggers the fault. It doesn’t seem to be related to the file count (numbers of files processed).

zilog · 2008-01-28T11:33:22.000Z

nyarnon post:1:

Hi there,

I was glad to see Avast for Linux as my experiences on the other operating system where very satisfying. I’m sorry I cannot say the same for my linux home server. Here I encounter segmentation faults. The error message in question is:

/usr/bin/avastgui: line 169: 23526 Segmentation fault $AVAST_PREFIX/bin/$programname $*

and also

/usr/bin/avast: line 169: 27770 Segmentation fault $AVAST_PREFIX/bin/$programname $*

I’m running on:

Linux siefu 2.6.22-3-686-bigmem #1 SMP Mon Nov 12 09:52:20 UTC 2007 i686 GNU/Linux

Is there some kind of debug switch to get some real debugging info. Just reporting the last line of the wrapper script isn’t very helpfull.

BTW seems that this happens every time it hits on the OLPC qemu image.

I have removed the file in question but now it just stops a few moments later on an other file. It’s always the same file till you remove it. Then another file triggers the fault. It doesn’t seem to be related to the file count (numbers of files processed).

Hallo, there’s no need to duplicate debugging on lower levels - You can do always things like this:
strace -f -i -s 1024 (cmdline as usually) >strace.log 2>&1

Run avast under strace, wait for the crash over that OLPC image, and send us the log. I’ll try to build fresh-new Workstation package, and i’ll post it here as beta.

Regards,
PC

system · 2008-01-29T22:44:28.000Z

Should have thought of that myself Anyway I send you the log by mail a few minutes ago. It was not the OLPC image after all but the next file. Hope you can come up with a solution.

zilog · 2008-01-31T18:12:32.000Z

nyarnon post:3:

Should have thought of that myself Anyway I send you the log by mail a few minutes ago. It was not the OLPC image after all but the next file. Hope you can come up with a solution.

Hallo,
I’m unable (at least for now) to reproduce the flaw on our testbed. Please, test this beta-build (avast or avastgui):

http://public.avast.com/~cimbal/avast4workstation_1.2.0beta-2_i386.deb

Two other problems were found, but not related to the filesize. Also, please, get rid of old shared blocks of crashed app - they might be damaged (quitting all apps that use libavastengine & doing ipcrm (or reboting) will do the job). Please, tell me whether this helped or not. If not, i’ll try to catch the bug again.

Regards,
PC

Announcements