4 Dynodump, not to be confused with DinoTurd (as seen in Jurassic Park),
5 is a shared object that provides one function:
7 int dynodump(char *new_file);
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
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):
21 char _foo[] = "hello";
22 char _bar[] = "world";
24 $ cc -G -o lib.so lib.c
27 extern char _foo, _bar;
36 (void) printf("%d: foo = %x\n", beenhere, foo);
37 (void) printf("%d: bar = %x, ", beenhere, bar);
44 (void) printf("%x\n", bar);
47 $ cc -o prog prog.c -R. lib.so dynodump.so
51 0: bar = ef7503d2, ef7503d3
55 1: bar = ef7503d2, ef7503d2
57 Notice that in the run of newfile, bar points at "world" instead of
58 the perhaps expected "orld".
60 Dynodump supports sparc, intel, and power pc architectures.
62 Dynodump is buildable with GNU make and gcc. If it works for you
63 with these tools, let me know.
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:
75 #define UNEXEC unexsol2.o
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.
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
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.
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."