Mercurial > emacs
view BUGS @ 73690:04b7851d50f8
(malloc_cookie): Remove unused variable.
(region_list_head, region_list_tail, lca, nlc, infile_lc_highest_addr)
(text_seg_lowest_offset, mh, curr_header_offset, infd, outfd)
(emacs_zone, data_segment_old_fileoff, data_segment_scp)
(num_unexec_regions, unexec_regions): Make variables static.
(print_regions, find_emacs_zone_regions): Make static.
(unexec_region_info): New typedef.
(unexec_regions): Change type from vm_range_t[] to unexec_region_info[].
All uses changed.
(unexec_regions_recorder): Subtract size of trailing null pages from
filesize. Show filesize.
(unexec_regions_merge): Don't merge if null pages of preceding region
is not too small. Use long format in printf.
(copy_segment, copy_data_segment): Show filesize.
(copy_data_segment): Write filesize bytes of region data. Adjust
filesize in segment command accordingly.
(dump_it): Use long format in printf.
author | YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> |
---|---|
date | Sun, 05 Nov 2006 06:11:54 +0000 |
parents | 8ce686bd7f4f |
children | fb8bf24d2eb9 |
line wrap: on
line source
If you think you may have found a bug in GNU Emacs, please read the Bugs section of the Emacs manual for advice on (1) how to tell when to report a bug, and (2) how to write a useful bug report and what information it needs to have. There are three ways to read the Bugs section. (1) In a printed copy of the Emacs manual. You can order one from the Free Software Foundation; see the file etc/ORDERS. But if you don't have a copy on hand and you think you have found a bug, you shouldn't wait to get a printed manual; you should read the section right away as described below. (2) With Info. Start Emacs, do C-h i to enter Info, then m Emacs RET to get to the Emacs manual, then m Bugs RET to get to the section on bugs. Or use standalone Info in a like manner. (Standalone Info is part of the Texinfo distribution, not part of the Emacs distribution.) (3) By hand. Do cat info/emacs* | more "+/^File: emacs, Node: Bugs," Please first check the file etc/PROBLEMS (e.g. with C-h C-e in Emacs) to make sure it isn't a known issue.