Mercurial > hg > xemacs-beta
view etc/toolbar/file-cap-up.xpm @ 2881:0e0af7cbfd1b
[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 | 3ecd8885ac67 |
| children | 7910031dd78a |
line wrap: on
line source
/* XPM */ static char * file[] = { "33 33 5 1", "X c Gray75 s backgroundToolBarColor", "u c #000000000000 s foregroundToolBarColor", "o c black", "O c white", "+ c Gray60", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXooooooooooXXXXXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOooXXXXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOo+oXXXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOo++oXXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOoooooXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX", "XXXXXXXXXXoOOOOOOOOOOOOoXXXXXXXXX", "XXXXXXXXXXooooooooooooooXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXuuuXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXuXXXuXuuuXXXuXXuuuXXXXXXX", "XXXXXXXXuXXXuXuXXuXuXuXuXXuXXXXXX", "XXXXXXXXuXXXuXuXXuXuuuXuXXuXXXXXX", "XXXXXXXXuXXXuXuXXuXuXXXuXXuXXXXXX", "XXXXXXXXXuuuXXuuuXXXuuXuXXuXXXXXX", "XXXXXXXXXXXXXXuXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"};