From: Eli Zaretskii <eliz@gnu.org>
To: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: Emacs 23.1.93 pretest
Date: Tue, 02 Mar 2010 20:15:14 +0200 [thread overview]
Message-ID: <834oky4mkt.fsf@gnu.org> (raw)
In-Reply-To: <83pr3pb1iu.fsf@gnu.org>
> Date: Sun, 28 Feb 2010 21:31:21 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc:
>
> So I think the change in charset.c itself did not cause the bug, it
> just exposed a bug elsewhere, because it reshuffles the heap.
Actually, it turns out it's not ``reshuffling the heap'' that triggers
the bug, but rather the fact that when we call xmalloc, Emacs might
relocate buffer text.
IOW, I found the reason for the bug. One of the callers of
load_charset_map_from_file maintains pointers into buffer text, so
when that gets relocated, ... you get the idea.
The first naive attempt to solve it was unsuccessful, so there's
probably something else at work here. Hmm...
next prev parent reply other threads:[~2010-03-02 18:15 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 3:40 Emacs 23.1.93 pretest Chong Yidong
2010-02-27 9:05 ` Eli Zaretskii
2010-02-27 10:21 ` Eli Zaretskii
2010-02-27 11:28 ` Juanma Barranquero
2010-02-27 12:11 ` Juanma Barranquero
2010-02-27 13:15 ` Eli Zaretskii
2010-02-27 14:14 ` Eli Zaretskii
2010-02-27 14:31 ` Andreas Schwab
2010-02-27 14:54 ` Eli Zaretskii
2010-02-27 14:59 ` Lennart Borgman
2010-02-27 15:29 ` Eli Zaretskii
2010-02-27 15:22 ` Chong Yidong
2010-02-27 18:58 ` Eli Zaretskii
2010-03-04 11:32 ` Kenichi Handa
2010-03-04 12:35 ` Jason Rumney
2010-02-27 15:39 ` Juanma Barranquero
2010-02-27 19:41 ` Stefan Monnier
2010-02-27 11:57 ` Eli Zaretskii
2010-02-27 19:03 ` Eli Zaretskii
2010-02-27 21:37 ` Chong Yidong
2010-02-27 22:22 ` Eli Zaretskii
2010-02-28 1:25 ` Chong Yidong
2010-02-28 17:21 ` Eli Zaretskii
2010-02-28 1:45 ` Chong Yidong
2010-02-28 10:46 ` Andreas Schwab
2010-02-28 14:25 ` Chong Yidong
2010-02-28 15:38 ` Andreas Schwab
2010-02-28 17:32 ` Eli Zaretskii
2010-02-28 19:31 ` Eli Zaretskii
2010-03-02 18:15 ` Eli Zaretskii [this message]
2010-03-02 19:53 ` Chong Yidong
2010-03-02 20:53 ` Eli Zaretskii
2010-03-04 11:24 ` Kenichi Handa
2010-02-28 17:34 ` Eli Zaretskii
2010-02-28 21:34 ` Chong Yidong
2010-02-28 17:15 ` Eli Zaretskii
2010-03-02 15:42 ` Drew Adams
2010-03-02 16:02 ` Chong Yidong
2010-03-02 18:35 ` Drew Adams
2010-03-02 19:53 ` Chong Yidong
2010-03-04 14:36 ` bug#5679: " Sergei Organov
-- strict thread matches above, loose matches on Subject: below --
2010-04-03 1:13 Chong Yidong
2010-04-03 1:34 ` Juanma Barranquero
2010-04-03 2:36 ` Chong Yidong
2010-04-03 2:38 ` Juanma Barranquero
2010-04-03 9:33 ` Eli Zaretskii
2010-04-03 12:45 ` Sean Sieger
2010-04-03 13:53 ` Eli Zaretskii
2010-04-03 15:06 ` Chong Yidong
2010-04-03 15:52 ` Eli Zaretskii
2010-04-03 1:45 ` Sean Sieger
2010-04-03 7:01 ` Eli Zaretskii
2010-04-03 8:26 ` Eli Zaretskii
2010-04-04 19:22 ` Drew Adams
2010-04-05 0:48 ` Sean Sieger
2010-04-11 18:30 ` Uwe Siart
2010-04-11 18:34 ` Uwe Siart
2010-04-05 9:33 ` Eduard Wiebe
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=834oky4mkt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--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).