comparison etc/PROBLEMS @ 106498:b151ed491d50

Remove resolved GTK on Cygwin problem.
author Chong Yidong <cyd@stupidchicken.com>
date Wed, 09 Dec 2009 01:07:36 +0000
parents da7a85775258
children 1d1d5d9bd884
comparison
equal deleted inserted replaced
106497:d06619fa1742 106498:b151ed491d50
242 crashes or exits unexpectedly and an attempt is made to create a new 242 crashes or exits unexpectedly and an attempt is made to create a new
243 frame on another X display, then a Gtk+ error happens in the emacs 243 frame on another X display, then a Gtk+ error happens in the emacs
244 server that results in an endless loop. This is not fixed in any known 244 server that results in an endless loop. This is not fixed in any known
245 Gtk+ version (2.14.4 being current). 245 Gtk+ version (2.14.4 being current).
246 246
247 ** Emacs compiled with Gtk+ crashes on startup on Cygwin.
248
249 A typical error message is
250 ***MEMORY-ERROR***: emacs[5172]: GSlice: failed to allocate 504 bytes
251 (alignment: 512): Function not implemented
252
253 Emacs supplies its own malloc, but glib (part of Gtk+) calls memalign and on
254 Cygwin, that becomes the Cygwin supplied memalign. As malloc is not the
255 Cygwin malloc, the Cygwin memalign always returns ENOSYS.
256
257 One workaround is to set G_SLICE=always-malloc before starting emacs.
258 For example, in bash,
259
260 G_SLICE=always-malloc emacs
261
262 or put
263
264 export G_SLICE=always-malloc
265
266 in one of the bash startup files. This also has to be done before
267 building emacs on Cygwin with Gtk+.
268
269 * General runtime problems 247 * General runtime problems
270 248
271 ** Lisp problems 249 ** Lisp problems
272 250
273 *** Changes made to .el files do not take effect. 251 *** Changes made to .el files do not take effect.