From: "Jan D." <jan.h.d@swipnet.se>
Cc: Nick Roberts <nickrob@snap.net.nz>,
emacs-devel@gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: Re: GC crashes
Date: Wed, 8 Dec 2004 07:04:15 +0100 [thread overview]
Message-ID: <FD2ADB28-48DE-11D9-8D09-000D93505B76@swipnet.se> (raw)
In-Reply-To: <200412080217.55955.pogonyshev@gmx.net>
>> Programs which are known not to work are:
>> * emacs starts up but immediately concludes it is out of memory
>> and
>> aborts. Emacs has it's own memory-management scheme, but I
>> don't
>> understand why this should interact so badly with Valgrind.
>> Emacs
>> works fine if you build it to use the standard malloc/free
>> routines.
>
> Then maybe someone should build it to use the standard malloc/free
> routines
> and try? (Yes, yes I should do it myself instead of bogging everybody
> else,
> but I don't have that much CPU time and I have not seen the infamous
> memory
> corruption yet, so I'm not that curious.)
I just tried that, but it failed in the same way.
Jan D.
next prev parent reply other threads:[~2004-12-08 6:04 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 14:32 Items in FOR-RELEASE Stefan
2004-12-06 19:52 ` Juri Linkov
2004-12-06 20:12 ` Stefan Monnier
2004-12-06 21:12 ` Juri Linkov
2004-12-06 21:45 ` Stefan Monnier
2004-12-06 22:33 ` Juri Linkov
2004-12-06 22:47 ` GC crashes (Was: Items in FOR-RELEASE) Juri Linkov
2004-12-07 9:37 ` GC crashes Kim F. Storm
2004-12-07 15:54 ` Paul Pogonyshev
2004-12-07 20:46 ` Jan D.
2004-12-07 20:53 ` Nick Roberts
2004-12-08 0:17 ` Paul Pogonyshev
2004-12-08 6:04 ` Jan D. [this message]
2004-12-08 7:31 ` Nick Roberts
2004-12-08 17:39 ` Eli Zaretskii
2004-12-08 19:27 ` Nick Roberts
2004-12-08 22:15 ` Richard Stallman
2004-12-08 1:34 ` Items in FOR-RELEASE Miles Bader
2004-12-08 3:14 ` Stefan Monnier
2004-12-08 22:15 ` Richard Stallman
2004-12-08 8:37 ` Kim F. Storm
2004-12-08 4:39 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2005-12-14 21:49 GC crashes Chong Yidong
2005-12-14 23:18 ` David Kastrup
2005-12-14 23:24 ` Chong Yidong
2005-12-14 23:28 ` David Kastrup
2005-12-17 19:52 ` Chong Yidong
2005-12-18 17:15 ` Richard M. Stallman
2003-11-24 10:09 Werner LEMBERG
2003-11-26 2:03 ` Kenichi Handa
2003-11-28 9:31 ` [mew-int 01653] " Werner LEMBERG
2003-12-01 12:40 ` [mew-int 01661] " Kenichi Handa
2003-12-02 16:25 ` Stefan Monnier
2003-12-02 23:37 ` [mew-int 01671] " Kenichi Handa
2003-12-03 17:25 ` Stefan Monnier
2003-12-03 23:19 ` Kenichi Handa
2003-12-04 0:29 ` Stefan Monnier
2003-12-04 1:12 ` Kenichi Handa
2003-12-04 2:21 ` Kenichi Handa
2003-12-04 15:48 ` Stefan Monnier
2003-12-08 2:31 ` Kenichi Handa
2003-12-08 2:52 ` Stefan Monnier
2003-12-08 5:01 ` Kenichi Handa
2003-12-08 5:16 ` Stefan Monnier
2003-12-08 6:05 ` Kenichi Handa
2003-12-08 6:25 ` Stefan Monnier
2003-12-08 7:14 ` Kenichi Handa
2003-11-26 14:24 ` Stefan Monnier
2003-12-02 7:01 ` Eli Zaretskii
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=FD2ADB28-48DE-11D9-8D09-000D93505B76@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
--cc=storm@cua.dk \
/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).