Mercurial > hg > xemacs-beta

comparison src/ChangeLog @ 2881:0e0af7cbfd1b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2005-08-01 16:28:18 by darrylo] On some (64-bit) systems, sizeof(int) != sizeof(long), and this can cause crashes because in-use lisp objects can get prematurely gc'd (and 0xdeadbeef'd). This occurs because the memory_description for the Gap_Array structure incorrectly describes some members as XD_INT's (32-bit objects), when they should actually be XD_ELEMCOUNT's and XD_BYTECOUNT's (both 64-bit objects), as that is how they are declared in the structure.
author darrylo
date Mon, 01 Aug 2005 16:28:21 +0000
parents 5bf18ccb05df
children 0d5322818981
comparison
equal deleted inserted replaced
2880:617b080c902f 2881:0e0af7cbfd1b
1 2005-07-29 Darryl Okahata <darrylo@xemacs.org>
2
3 * extents.c (lispobj_gap_array_description_1): fix the memory
4 descriptions for the "gap", "offset_past_gap", and "els_past_gap"
5 members. Before, they were incorrectly defined as "XD_INT"
6 objects. They've been corrected to use "XD_ELEMCOUNT" and
7 "XD_BYTECOUNT", as that is how they are defined in the actual
8 Gap_Array declaration. This is important on systems where
9 sizeof(int) != sizeof(long), such as some 64-bit systems.
10
1 2005-07-24 Fabrice Popineau <Fabrice.Popineau@supelec.fr> 11 2005-07-24 Fabrice Popineau <Fabrice.Popineau@supelec.fr>
2 12
3 * frame-msw.c (mswindows_set_frame_size): Don't have a frame size 13 * frame-msw.c (mswindows_set_frame_size): Don't have a frame size
4 change trigger restoring the frame. 14 change trigger restoring the frame.
5 15