From: "Håkon Alstadheim" <hakon@alstadheim.priv.no>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Program received signal SIGSEGV, Segmentation fault.
Date: Sat, 14 Aug 2004 10:20:58 +0200 [thread overview]
Message-ID: <200408140820.i7E8KwnS007283@alstadheim.priv.no> (raw)
In-Reply-To: Your message of "Fri, 13 Aug 2004 23:26:16 +0200." <jevffmbuh3.fsf@sykes.suse.de>
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.
next prev parent reply other threads:[~2004-08-14 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 20:39 Program received signal SIGSEGV, Segmentation fault Håkon Alstadheim
2004-08-13 21:26 ` Andreas Schwab
2004-08-14 8:20 ` Håkon Alstadheim [this message]
2004-08-21 19:27 ` Håkon Alstadheim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200408140820.i7E8KwnS007283@alstadheim.priv.no \
--to=hakon@alstadheim.priv.no \
--cc=bug-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).