From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org, mew-int@mew.org
Subject: [mew-int 01661] Re: GC crashes
Date: Mon, 1 Dec 2003 21:40:27 +0900 (JST) [thread overview]
Message-ID: <200312011240.VAA05762@etlken.m17n.org> (raw)
In-Reply-To: <20031128.103107.41640217.wl@gnu.org> (message from Werner LEMBERG on Fri, 28 Nov 2003 10:31:07 +0100 (CET))
In article <20031128.103107.41640217.wl@gnu.org>, Werner LEMBERG <wl@gnu.org> writes:
> [1 <text/plain; us-ascii (7bit)>]
>> Please find a way to reproduce this bug by emacs started
>> with -q.
> I can't :-( It seems to be an interaction with running mewl (a program
> from the mew package which extracts header information from emails,
> sending them to the +inbox buffer) and ctext encoding. mewl runs as a
> background process; I normally start reading the emails while mewl is
> still running, augmenting the current buffer with header lines. So
> the bug seems to be that visiting a buffer in ctext encoding which is
> still augmented, and which contains many different scripts, causes a
> crash.
Thank you. It's a useful information. Now I can reproduce
the similar misterious segfault in GC without process nor
code conversion. I've just installed the attached change.
It seems that it fixes the problem, but I still don't
understand why a week hash table causes a problem. Anyway,
could you please try again with the latest CVS HEAD?
The strange thing is that the change for making a
composition hash table weak is done on 2003-01-10, about a
year ago. I don't know why the current problem appears
recently for you.
---
Ken'ichi HANDA
handa@m17n.org
Index: composite.c
===================================================================
RCS file: /cvsroot/emacs/emacs/src/composite.c,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -c -r1.29 -r1.30
cvs server: conflicting specifications of output style
*** composite.c 1 Sep 2003 15:45:52 -0000 1.29
--- composite.c 1 Dec 2003 12:33:13 -0000 1.30
***************
*** 843,849 ****
args[0] = QCtest;
args[1] = Qequal;
args[2] = QCweakness;
! args[3] = Qt;
args[4] = QCsize;
args[5] = make_number (311);
composition_hash_table = Fmake_hash_table (6, args);
--- 843,851 ----
args[0] = QCtest;
args[1] = Qequal;
args[2] = QCweakness;
! /* Fixme: It seems that a weak hash table leads to segfault in GC,
! but I have not yet found why. -- handa@m17n.org */
! args[3] = Qnil;
args[4] = QCsize;
args[5] = make_number (311);
composition_hash_table = Fmake_hash_table (6, args);
next prev parent reply other threads:[~2003-12-01 12:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 10:09 GC crashes Werner LEMBERG
2003-11-26 2:03 ` Kenichi Handa
2003-11-28 9:31 ` [mew-int 01653] " Werner LEMBERG
2003-12-01 12:40 ` Kenichi Handa [this message]
2003-12-02 8:31 ` [mew-int 01666] " Werner LEMBERG
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-03 23:58 ` [mew-int 01678] " Stefan Monnier
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=200312011240.VAA05762@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=mew-int@mew.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).