make lrecord UID's have a separate UID space for each object, resurrect debug SOE code in extents.c -------------------- ChangeLog entries follow: -------------------- src/ChangeLog addition: 2010-03-15 Ben Wing <ben@xemacs.org> * alloc.c: * alloc.c (c_readonly): * alloc.c (deadbeef_memory): * alloc.c (make_compiled_function): * alloc.c (make_button_data): * alloc.c (make_motion_data): * alloc.c (make_process_data): * alloc.c (make_timeout_data): * alloc.c (make_magic_data): * alloc.c (make_magic_eval_data): * alloc.c (make_eval_data): * alloc.c (make_misc_user_data): * alloc.c (noseeum_make_marker): * alloc.c (ADDITIONAL_FREE_string): * alloc.c (common_init_alloc_early): * alloc.c (init_alloc_once_early): * bytecode.c (print_compiled_function): * bytecode.c (mark_compiled_function): * casetab.c: * casetab.c (print_case_table): * console.c: * console.c (print_console): * database.c (print_database): * database.c (finalize_database): * device-msw.c (sync_printer_with_devmode): * device-msw.c (print_devmode): * device-msw.c (finalize_devmode): * device.c: * device.c (print_device): * elhash.c: * elhash.c (print_hash_table): * eval.c (print_multiple_value): * eval.c (mark_multiple_value): * events.c (deinitialize_event): * events.c (print_event): * events.c (event_equal): * extents.c: * extents.c (soe_dump): * extents.c (soe_insert): * extents.c (soe_delete): * extents.c (soe_move): * extents.c (extent_fragment_update): * extents.c (print_extent_1): * extents.c (print_extent): * extents.c (vars_of_extents): * frame.c: * frame.c (print_frame): * free-hook.c: * free-hook.c (check_free): * glyphs.c: * glyphs.c (print_image_instance): * glyphs.c (print_glyph): * gui.c: * gui.c (copy_gui_item): * hash.c: * hash.c (NULL_ENTRY): * hash.c (KEYS_DIFFER_P): * keymap.c (print_keymap): * keymap.c (MARKED_SLOT): * lisp.h: * lrecord.h: * lrecord.h (LISP_OBJECT_UID): * lrecord.h (set_lheader_implementation): * lrecord.h (struct old_lcrecord_header): * lstream.c (print_lstream): * lstream.c (finalize_lstream): * marker.c (print_marker): * marker.c (marker_equal): * mc-alloc.c (visit_all_used_page_headers): * mule-charset.c: * mule-charset.c (print_charset): * objects.c (print_color_instance): * objects.c (print_font_instance): * objects.c (finalize_font_instance): * opaque.c (print_opaque): * opaque.c (print_opaque_ptr): * opaque.c (equal_opaque_ptr): * print.c (internal_object_printer): * print.c (enum printing_badness): * rangetab.c (print_range_table): * rangetab.c (range_table_equal): * specifier.c (print_specifier): * specifier.c (finalize_specifier): * symbols.c: * symbols.c (print_symbol_value_magic): * tooltalk.c: * tooltalk.c (print_tooltalk_message): * tooltalk.c (print_tooltalk_pattern): * window.c (print_window): * window.c (debug_print_window): (1) Make lrecord UID's have a separate UID space for each object. Otherwise, with 20-bit UID's, we rapidly wrap around, especially when common objects like conses and strings increment the UID value for every object created. (Originally I tried making two UID spaces, one for objects that always print readably and hence don't display the UID, and one for other objects. But certain objects like markers for which a UID is displayed are still generated rapidly enough that UID overflow is a serious issue.) This also has the advantage of making UID values smaller, hence easier to remember -- their main purpose is to make it easier to keep track of different objects of the same type when debugging code. Make sure we dump lrecord UID's so that we don't have problems with pdumped and non-dumped objects having the same UID. (2) Display UID's consistently whenever an object (a) doesn't consistently print readably (objects like cons and string, which always print readably, can't display a UID), and (b) doesn't otherwise have a unique property that makes objects of a particular type distinguishable. (E.g. buffers didn't and still don't print an ID, but the buffer name uniquely identifies the buffer.) Some types, such as event, extent, compiled-function, didn't always (or didn't ever) display an ID; others (such as marker, extent, lstream, opaque, opaque-ptr, any object using internal_object_printer()) used to display the actual machine pointer instead. (3) Rename NORMAL_LISP_OBJECT_UID to LISP_OBJECT_UID; make it work over all Lisp objects and take a Lisp object, not a struct pointer. (4) Some misc cleanups in alloc.c, elhash.c. (5) Change code in events.c that "deinitializes" an event so that it doesn't increment the event UID counter in the process. Also use deadbeef_memory() to overwrite memory instead of doing the same with custom code. In the process, make deadbeef_memory() in alloc.c always available, and delete extraneous copy in mc-alloc.c. Also capitalize all uses of 0xDEADBEEF. Similarly in elhash.c call deadbeef_memory(). (6) Resurrect "debug SOE" code in extents.c. Make it conditional on DEBUG_XEMACS and on a `debug-soe' variable, rather than on SOE_DEBUG. Make it output to stderr, not stdout. (7) Delete some custom print methods that were identical to external_object_printer().

Package distributions may be placed in this directory.
If present and a package-path is configured, packages can be installed
using the top-level Makefile.

To configure the package path, use the --with-late-packages option to
configure, which specifies a single directory in which to install the
xemacs-packages and mule-packages hierarchies provided.  If this is null,
or contains a Unix-style search path (i.e., a colon is present in the
argument of the --with-late-packages option), you will have to install
the packages by hand.

To find out if a distribution includes bundled packages, type

    make check-available-packages

There are three Make targets that may be available depending on the package
sets supplied.

    make install-bootstrap-packages
        Install a selected set of packages sufficient to support
        downloading and installing packages via the M-x list-packages
        interface.  Chose this if you want to be able to install the
        latest version of each package immediately.

    make install-nomule-packages
        Install the full distribution of packages that do not require a
        Mule-enabled XEmacs.  Choose this package if you don't have a
        Mule-enabled XEmacs and want the convenience of a single-command
        installation.  You can add or update packages via M-x list-packages
        at any time.

    make install-all-packages
        Install the full distribution of packages, including those requiring
        a Mule-enabled XEmacs.  Choose this package if you have a Mule-
        enabled XEmacs and want the convenience of a single-command
        installation.  You can add or update packages via M-x list-packages
        at any time.

DISTRIBUTOR'S NOTE: you may choose what packages you wish to include in
bootstrap.tar.gz, but to make list-packages work you need to include at
least xemacs-base, dired, and efs.  The tarball should unpack directly as
an xemacs-packages tree (and optionaly, a mule-packages tree.  Also, if
either of xemacs-sumo.tar.gz or xemacs-mule-sumo.tar.gz is provided, the
other should be as well.

If packages are not available with the distribution, you can get them at

    ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-sumo.tar.gz
    ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-mule-sumo.tar.gz
    http://turnbull.sk.tsukuba.ac.jp/Tools/XEmacs/bootstrap.tar.gz

and place them in the same directory as this file.  You can also make your
own bootstrap.tar.gz by creating a directory xemacs-packages, then
untarring the packages of your choice into that directory, and tarring the
whole thing up with "tar czf bootstrap.tar.gz xemacs-packages".  (If you
wish to include mule-packages, you should place them in mule-packages as
a sibling of xemacs-packages.)

This facility currently does not support installations which configure
the --with-early-packages, --with-late-packages, or --with-last-packages
options.

This facility currently will not overwrite an existing package
installation, not even if a whole hierarchy (usually the mule-packages)
is missing.  In particular, you cannot use this feature to add the
mule-packages to a package installation which lacks them, even if the
hierarchy is missing, or the xemacs-packages hierarchy was installed
this way.  Nor can you "upgrade" a bootstrap installation to a full
installation.  If you wish to do any of these things you will need to
remove the existing hierarchies.