Mercurial > hg > xemacs-beta
annotate dynodump/README @ 4477:e34711681f30
Don't determine whether to call general device-type code at startup,
rather decide in the device-specific code itself.
lisp/ChangeLog addition:
2008-07-07 Aidan Kehoe <kehoea@parhasard.net>
Patch to make it up to the device-specific code whether
various Lisp functions should be called during device creation,
not relying on the startup code to decide this. Also, rename
initial-window-system to initial-device-type (which makes more
sense in this scheme), always set it.
* startup.el (command-line):
Use initial-device-type, not initial-window-system; just call
#'make-device, leave the special behaviour to be done the first
time a console type is initialised to be decided on by the
respective console code.
* x-init.el (x-app-defaults-directory): Declare that it should be
bound.
(x-define-dead-key): Have the macro take a DEVICE argument.
(x-initialize-compose): Have the function take a DEVICE argument,
and use it when checking if various keysyms are available on the
keyboard.
(x-initialize-keyboard): Have the function take a DEVICE argument,
allowing device-specific keyboard initialisation.
(make-device-early-x-entry-point-called-p): New.
(make-device-late-x-entry-point-called-p): New. Rename
pre-x-win-initted, x-win-initted.
(make-device-early-x-entry-point): Rename init-pre-x-win, take the
call to make-x-device out (it should be called from the
device-creation code, not vice-versa).
(make-device-late-x-entry-point): Rename init-post-x-win, have it
take a DEVICE argument, use that DEVICE argument when working out
what device-specific things need doing. Don't use
create-console-hook in core code.
* x-win-xfree86.el (x-win-init-xfree86): Take a DEVICE argument;
use it.
* x-win-sun.el (x-win-init-sun): Take a DEVICE argument; use it.
* mule/mule-x-init.el: Remove #'init-mule-x-win, an empty
function.
* tty-init.el (make-device-early-tty-entry-point-called-p): New.
Rename pre-tty-win-initted.
(make-device-early-tty-entry-point): New.
Rename init-pre-tty-win.
(make-frame-after-init-entry-point): New.
Rename init-post-tty-win to better reflect when it's called.
* gtk-init.el (gtk-early-lisp-options-file): New.
Move this path to a documented variable.
(gtk-command-switch-alist): Wrap the docstring to fewer than 79
columns.
(make-device-early-gtk-entry-point-called-p): New.
(make-device-late-gtk-entry-point-called-p): New.
Renamed gtk-pre-win-initted, gtk-post-win-initted to these.
(make-device-early-gtk-entry-point): New.
(make-device-late-gtk-entry-point): New.
Renamed init-pre-gtk-win, init-post-gtk-win to these.
Have make-device-late-gtk-entry-point take a device argument, and use
it; have make-device-early-gtk-entry-point load the GTK-specific
startup code, instead of doing that in C.
(init-gtk-win): Deleted, functionality moved to the GTK device
creation code.
(gtk-define-dead-key): Have it take a DEVICE argument; use this
argument.
(gtk-initialize-compose): Ditto.
* coding.el (set-terminal-coding-system):
Correct the docstring; the function isn't broken.
src/ChangeLog addition:
2008-07-07 Aidan Kehoe <kehoea@parhasard.net>
Patch to make it up to the device-specific code whether
various Lisp functions should be called during device creation,
not relying on the startup code to decide this. Also, rename
initial-window-system to initial-device-type (which makes more
sense in this scheme), always set it.
* redisplay.c (Vinitial_device_type): New.
(Vinitial_window_system): Removed.
Rename initial-window-system to initial-device type, making it
a stream if we're noninteractive. Update its docstring.
* device-x.c (Qmake_device_early_x_entry_point,
Qmake_device_late_x_entry_point): New.
Rename Qinit_pre_x_win, Qinit_post_x_win.
(x_init_device): Call #'make-device-early-x-entry-point earlier,
now we rely on it to find the application class and the
app-defaults directory.
(x_finish_init_device): Call #'make-device-late-x-entry-point with
the created device.
(Vx_app_defaults_directory): Always make this available, to
simplify code in x-init.el.
* device-tty.c (Qmake_device_early_tty_entry_point): New.
Rename Qinit_pre_tty_win, rename Qinit_post_tty_win and move to
frame-tty.c as Qmake_frame_after_init_entry_point.
(tty_init_device): Call #'make-device-early-tty-entry-point before
doing anything.
* frame-tty.c (Qmake_frame_after_init_entry_point): New.
* frame-tty.c (tty_after_init_frame): Have it call the
better-named #'make-frame-after-init-entry-point function
instead of #'init-post-tty-win (since it's called after frame, not
device, creation).
* device-msw.c (Qmake_device_early_mswindows_entry_point,
Qmake_device_late_mswindows_entry_point): New.
Rename Qinit_pre_mswindows_win, Qinit_post_mswindows_win.
(mswindows_init_device): Call
#'make-device-early-mswindows-entry-point here, instead of having
its predecessor call us.
(mswindows_finish_init_device): Call
#'make-device-early-mswindows-entry-point, for symmetry with the
other device types (though it's an empty function).
* device-gtk.c (Qmake_device_early_gtk_entry_point,
Qmake_device_late_gtk_entry_point): New.
Rename Qinit_pre_gtk_win, Qinit_post_gtk_win.
(gtk_init_device): Call #'make-device-early-gtk-entry-point; don't
load ~/.xemacs/gtk-options.el ourselves, leave that to lisp.
(gtk_finish_init_device): Call #'make-device-late-gtk-entry-point
with the created device as an argument.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Wed, 09 Jul 2008 20:46:22 +0200 |
| parents | 376386a54a3c |
| children |
| rev | line source |
|---|---|
| 0 | 1 DYNODUMP |
| 2 -------- | |
| 3 | |
| 4 Dynodump, not to be confused with DinoTurd (as seen in Jurassic Park), | |
| 5 is a shared object that provides one function: | |
| 6 | |
| 7 int dynodump(char *new_file); | |
| 8 | |
| 9 dynodump(), called from a running program will write a new executable | |
| 10 in new_file a la unexec() in GNU Emacs. The difference lies in the | |
| 11 relocations. | |
| 12 | |
| 13 dynodump() will create an image with any relocations (which were | |
| 14 performed by the run-time dynamic linker) undone. This allows the new | |
| 15 image to be run in a different environment. There is, however, one | |
| 16 potentially major caveat. If a symbol reference gets updated during | |
| 17 the running of the calling program, its updated value will be lost. | |
| 18 An example (with additional blank lines for legibility): | |
| 19 | |
| 20 $ cat lib.c | |
| 21 char _foo[] = "hello"; | |
| 22 char _bar[] = "world"; | |
| 23 | |
| 24 $ cc -G -o lib.so lib.c | |
| 25 | |
| 26 $ cat prog.c | |
| 27 extern char _foo, _bar; | |
| 28 | |
| 29 int beenhere = 0; | |
| 30 char * foo = &_foo; | |
| 31 char * bar = &_bar; | |
| 32 | |
| 33 int | |
| 34 main(void) | |
| 35 { | |
| 36 (void) printf("%d: foo = %x\n", beenhere, foo); | |
| 37 (void) printf("%d: bar = %x, ", beenhere, bar); | |
| 38 | |
| 39 if (!beenhere) { | |
| 40 beenhere = 1; | |
| 41 bar++; | |
| 42 dynodump("newfile"); | |
| 43 } | |
| 44 (void) printf("%x\n", bar); | |
| 45 } | |
| 46 | |
| 47 $ cc -o prog prog.c -R. lib.so dynodump.so | |
| 48 | |
| 49 $ ./prog | |
| 50 0: foo = ef7503cc | |
| 51 0: bar = ef7503d2, ef7503d3 | |
| 52 | |
| 53 $ ./newfile | |
| 54 1: foo = ef7503cc | |
| 55 1: bar = ef7503d2, ef7503d2 | |
| 56 | |
| 57 Notice that in the run of newfile, bar points at "world" instead of | |
| 58 the perhaps expected "orld". | |
| 59 | |
| 60 Dynodump supports sparc, intel, and power pc architectures. | |
| 61 | |
| 62 Dynodump is buildable with GNU make and gcc. If it works for you | |
| 63 with these tools, let me know. | |
| 64 | |
| 65 unexec() | |
| 66 -------- | |
| 67 | |
| 68 Also supplied is an unexsol2.c which belongs in the XEmacs src | |
| 69 directory with the other unex*.c files. The src/s/sol2.h should be | |
| 70 have the following added to it: | |
| 71 | |
| 72 #ifdef UNEXEC | |
| 73 #undef UNEXEC | |
| 74 #endif | |
| 75 #define UNEXEC unexsol2.o | |
| 76 | |
| 77 This unexec() will attempt to dlopen() the dynodump.so to find the | |
| 78 dynodump function. The default is "../dynodump/dynodump.so" which | |
| 79 should be appropriate for the typical XEmacs build (unless you used | |
| 80 configure to set up separate build and source trees). You may change | |
| 81 it by setting the DYNODUMP environment variable to the full path of | |
| 82 the dynodump shared object. | |
| 83 | |
| 84 Other notes: | |
| 85 | |
| 86 If you're using the 4.0 C compiler from Sun, you should arrange to | |
| 87 shut off the incremental linker. This is done with the -xildoff | |
| 88 option to the compiler. The common.mk and testsuite/Makefile files | |
| 89 have commentary and ready made lines for uncommenting for this | |
| 90 purpose. | |
| 91 | |
| 92 If you're interested in playing with the UltraSPARC specific options | |
| 93 to the aforementioned compiler, then the same makefiles have some | |
| 94 commentary and flags settings to point you in that direction. | |
| 95 | |
| 96 Questions: | |
| 97 | |
| 98 dynodump() was developed by Rod.Evans@Eng.Sun.COM and | |
| 99 Georg.Nikodym@Canada.Sun.COM. If you have questions, feel free to ask | |
| 100 them but be aware that Rod, "don't know jack about emacs." | |
| 101 |