From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: dak@gnu.org, schwab@linux-m68k.org, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r116836: Avoid GC crashes.
Date: Sun, 23 Mar 2014 21:09:53 +0200 [thread overview]
Message-ID: <83a9cg3f5q.fsf@gnu.org> (raw)
In-Reply-To: <532F2DE7.6050303@dancol.org>
> Date: Sun, 23 Mar 2014 11:54:31 -0700
> From: Daniel Colascione <dancol@dancol.org>
> CC: dak@gnu.org, rms@gnu.org, emacs-devel@gnu.org
>
> > There were several crashes in GC reported since October, at least some
> > of them might be related. In bug#16901, Dmitry mentioned some of
> > them, but there are more.
>
> I thought you found something wrong with gmalloc to explain that one.
Unfortunately, no. What I found was that the debugging code in
gmalloc had a bugthat would flag correct code as buggy. Once those
bugs were fixed, no memory-related problems were ever reported by
gmalloc.
next prev parent reply other threads:[~2014-03-23 19:09 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1WR8jg-0006nL-At@vcs.savannah.gnu.org>
2014-03-21 23:41 ` [Emacs-diffs] trunk r116836: Avoid GC crashes Daniel Colascione
2014-03-21 23:59 ` Glenn Morris
2014-03-22 2:35 ` Glenn Morris
2014-03-21 23:59 ` Juanma Barranquero
2014-03-22 1:22 ` Daniel Colascione
2014-03-22 1:29 ` Juanma Barranquero
2014-03-22 1:37 ` Daniel Colascione
2014-03-22 2:30 ` Stefan Monnier
2014-03-22 6:41 ` David Kastrup
2014-03-22 23:56 ` Richard Stallman
2014-03-23 7:12 ` Andreas Schwab
2014-03-23 16:07 ` Eli Zaretskii
2014-03-23 18:54 ` Daniel Colascione
2014-03-23 19:09 ` Eli Zaretskii [this message]
2014-03-23 19:53 ` Daniel Colascione
2014-03-23 20:10 ` Eli Zaretskii
2014-03-23 20:36 ` Daniel Colascione
2014-03-23 20:55 ` David Kastrup
2014-03-24 3:45 ` Eli Zaretskii
2014-03-23 20:59 ` Daniel Colascione
2014-03-24 16:48 ` Eli Zaretskii
2014-03-25 12:42 ` Richard Stallman
2014-03-25 12:49 ` Daniel Colascione
2014-03-25 22:41 ` Richard Stallman
2014-03-25 22:43 ` Daniel Colascione
2014-03-25 15:24 ` Dmitry Antipov
2014-03-25 18:01 ` Eli Zaretskii
2014-03-25 22:40 ` Richard Stallman
2014-03-25 15:43 ` Eli Zaretskii
2014-03-25 22:39 ` Richard Stallman
2014-03-26 3:49 ` Eli Zaretskii
2014-03-26 13:46 ` Richard Stallman
2014-03-26 15:24 ` Eli Zaretskii
2014-03-24 5:50 ` Ivan Andrus
2014-03-24 16:51 ` Eli Zaretskii
2014-03-24 17:12 ` Ivan Andrus
2014-03-22 23:57 ` Richard Stallman
2014-03-23 0:14 ` Daniel Colascione
2014-03-23 3:58 ` Eli Zaretskii
2014-03-23 7:05 ` Andreas Schwab
2014-03-23 16:05 ` Eli Zaretskii
2014-03-23 16:27 ` Andreas Schwab
2014-03-23 14:56 ` Richard Stallman
2014-03-22 23:57 ` Richard Stallman
2014-03-26 14:42 ` Rüdiger Sonderfeld
2014-03-27 17:47 ` Eli Zaretskii
2014-03-28 14:27 ` gNewSense QEMU setup [Was: Re: [Emacs-diffs] trunk r116836: Avoid GC crashes] Dmitry Antipov
2014-03-28 23:17 ` Richard Stallman
2014-03-29 0:00 ` Daniel Colascione
2014-03-30 0:24 ` Richard Stallman
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=83a9cg3f5q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dak@gnu.org \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.