From: John Covici <covici@ccs.covici.com>
To: emacs-devel@gnu.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: reading a file in emacs crashes 2.4.17 and 18-pre4
Date: Wed, 23 Jan 2002 05:11:09 -0500 [thread overview]
Message-ID: <m3elkh2x8i.fsf@ccs.covici.com> (raw)
In-Reply-To: <m38zardsps.fsf@ccs.covici.com>
In-Reply-To: <m38zardsps.fsf@ccs.covici.com> (John Covici's message of "Mon, 21 Jan 2002 21:28:47 -0500")
Well, I have worked around this problem by getting rid of the Athlon
optimizations so I guess there is still more work to do on those.
on Mon, 21 Jan 2002 21:28:47 -0500 John Covici <covici@ccs.covici.com> wrote:
> Its a small file and was actually an accident, but you get all sorts
> of unable to handle kernel paging ... and eventually a kernel panic
> because it was trying to kill the idle process.
>
> I am using emacs version "21.2.50.1" and I have 1.4ghz Athlon and 256
> m of memory.
--
John Covici
covici@ccs.covici.com
next prev parent reply other threads:[~2002-01-23 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 2:28 reading a file in emacs crashes 2.4.17 and 18-pre4 John Covici
2002-01-23 10:11 ` John Covici [this message]
2002-01-23 10:16 ` Eli Zaretskii
2002-01-23 11:45 ` John Covici
2002-01-23 16:30 ` Mark Hahn
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3elkh2x8i.fsf@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=emacs-devel@gnu.org \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox