From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Fix to long-standing crashes in GC
Date: 13 May 2004 15:19:26 -0400 [thread overview]
Message-ID: <87brks5e94.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <40A3BC23.8060000@math.ku.dk>
> interested, but I have not been able produce a test case. To me it looks as
> if GC is involved, but I am unexperienced with gdb. When Kim told he had
When the GC seems to be involved what it typically means that there's
a memory corruption somewhere. The only reason why the GC gets involved is
because the GC traverses all your memory, so it basically does (as a side
effect) some kind of sanity check, so memory corruption is usually detected
during GC. GC bugs exist as well, of course, but they're pretty rare (or
rather they tend to manifest pretty often, so they get fixed fairly quikly).
Stefan
next prev parent reply other threads:[~2004-05-13 19:19 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 18:19 Fix to long-standing crashes in GC Lars Hansen
2004-05-13 19:09 ` Luc Teirlinck
2004-05-13 19:29 ` Luc Teirlinck
2004-05-13 19:30 ` Lars Hansen
2004-05-13 19:19 ` Stefan Monnier [this message]
2004-05-13 22:16 ` Luc Teirlinck
2004-05-13 23:04 ` Stefan Monnier
2004-05-14 11:42 ` Kai Grossjohann
2004-05-14 14:53 ` Luc Teirlinck
2004-05-14 20:48 ` Kai Grossjohann
2004-05-16 9:27 ` Kai Grossjohann
2004-05-14 18:39 ` Luc Teirlinck
2004-05-14 20:54 ` Kim F. Storm
2004-05-14 21:02 ` Richard Stallman
2004-05-22 18:09 ` Lars Hansen
2004-05-23 16:33 ` Eli Zaretskii
2004-05-23 16:32 ` Luc Teirlinck
2004-05-23 17:11 ` Lars Hansen
2004-05-24 5:30 ` Eli Zaretskii
2004-05-25 3:03 ` Luc Teirlinck
2004-05-25 7:07 ` Eli Zaretskii
2004-05-15 4:39 ` Robert Marshall
2004-05-17 14:39 ` Kim F. Storm
2004-05-17 17:42 ` Robert Marshall
2004-05-17 14:43 ` Kim F. Storm
2004-05-18 0:13 ` Luc Teirlinck
2004-05-19 1:26 ` Richard Stallman
2004-05-19 12:11 ` Kim F. Storm
2004-05-19 19:32 ` Stefan Monnier
2004-05-19 22:33 ` Kim F. Storm
2004-05-20 13:17 ` Richard Stallman
2004-05-19 12:52 ` Kim F. Storm
2004-05-19 16:48 ` Stefan Monnier
2004-05-19 22:04 ` Kim F. Storm
2004-05-19 22:25 ` Stefan Monnier
2004-05-19 22:37 ` Kim F. Storm
2004-05-19 22:50 ` Stefan Monnier
2004-05-20 0:44 ` Kim F. Storm
2004-05-21 23:43 ` Kim F. Storm
2004-05-23 1:14 ` Stefan Monnier
2004-05-23 18:28 ` Richard Stallman
2004-05-24 11:57 ` Kim F. Storm
2004-05-28 21:51 ` Stefan Monnier
2004-05-28 23:40 ` Kim F. Storm
2004-05-28 23:49 ` Stefan Monnier
2004-05-29 23:15 ` Kim F. Storm
2004-05-30 20:44 ` Stefan Monnier
2004-05-31 20:21 ` Kim F. Storm
2004-06-08 20:03 ` Lars Hansen
2004-05-20 7:08 ` Richard Stallman
2004-05-21 22:58 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2004-05-13 23:34 Robert Anderson
2004-05-12 13:19 Kim F. Storm
2004-05-13 13:06 ` Kenichi Handa
2004-05-13 15:45 ` 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
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=87brks5e94.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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).