From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: CVS problems
Date: Wed, 3 Dec 2003 20:59:36 +0900 (JST) [thread overview]
Message-ID: <200312031159.UAA03378@etlken.m17n.org> (raw)
In-Reply-To: <20031203.122154.42791409.wl@gnu.org> (message from Werner LEMBERG on Wed, 03 Dec 2003 12:21:54 +0100 (CET))
In article <20031203.122154.42791409.wl@gnu.org>, Werner LEMBERG <wl@gnu.org> writes:
> Since two days I can't update the emacs CVS (and all other CVS
> repositories from subversions. I always get the message
> cvs [update aborted]: end of file from server
> (consult above messages if any)
> Is this a known problem?
I don't have that problem. Actually I commited some changes
today. Anyway, the patch for segfault is just as attached.
Could you apply it to your local file and test it?
---
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);
prev parent reply other threads:[~2003-12-03 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 11:21 CVS problems Werner LEMBERG
2003-12-03 11:59 ` Kenichi Handa [this message]
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=200312031159.UAA03378@etlken.m17n.org \
--to=handa@m17n.org \
--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 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.