[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Program received signal SIGSEGV, Segmentation fault.
From: |
Håkon Alstadheim |
Subject: |
Re: Program received signal SIGSEGV, Segmentation fault. |
Date: |
Sat, 14 Aug 2004 10:20:58 +0200 |
In message <jevffmbuh3.fsf@sykes.suse.de>, Andreas Schwab writes:
>"Håkon Alstadheim" <haalst@online.no> writes:
>
>> After using emacs for some time, it crashes.
>
>Are you sure your hardware is OK? Please try running memtest to rule out
>memory problems.
>
I booted into memtest after I got Andreas' mail and let it run for 7
hours. No reports of anything amiss.
This thing is really bugging me. I'm guessing I'm getting about two
hours between crashes when I'm reading news or doing anything else
heavy duty. I keep an emacs with an inferior lisp process and nothing
else running, and that stays alive for several days, averaging about
100 to 1000 new lines a day in the *inferior-lisp* buffer. We can
definitely say that wallclock time is not the main triggering factor.
I also have mozilla staying alive constantly, So I'd say all my RAM is
exersized by that without any ill effects.
>> REPORT 2:
>> After viewing some .tgz files and during "tar xzvf" in a shell buffer
>> Bogus stacktrace? Fgargage collect is not on line 1635!!
>
>But compact_small_strings is a static function, thus eligible for inlining
>with -funit-at-a-time.
Ah, OK.