Debian Codegraph @

external/bdwgc/doc/README.solaris2

raw
1 The collector supports both incremental collection and threads under
2 Solaris 2. The incremental collector normally retrieves page dirty information
3 through the appropriate /proc calls. But it can also be configured
4 (by defining MPROTECT_VDB instead of PROC_VDB in gcconfig.h) to use mprotect
5 and signals. This may result in shorter pause times, but it is no longer
6 safe to issue arbitrary system calls that write to the heap.
7
8 Under other UNIX versions,
9 the collector normally obtains memory through sbrk. There is some reason
10 to expect that this is not safe if the client program also calls the system
11 malloc, or especially realloc. The sbrk man page strongly suggests this is
12 not safe: "Many library routines use malloc() internally, so use brk()
13 and sbrk() only when you know that malloc() definitely will not be used by
14 any library routine." This doesn't make a lot of sense to me, since there
15 seems to be no documentation as to which routines can transitively call malloc.
16 Nonetheless, under Solaris2, the collector now allocates
17 memory using mmap by default. (It defines USE_MMAP in gcconfig.h.)
18 You may want to reverse this decisions if you use -DREDIRECT_MALLOC=...
19
20 Note:
21 Before you run "make check", you need to set your LD_LIBRARY_PATH correctly
22 (e.g., to "/usr/local/lib") so that tests can find the shared library
23 libgcc_s.so.1. Alternatively, you can configure with --disable-shared.
24
25 SOLARIS THREADS:
26
27 Unless --disable-threads option is given, threads support is on by default in
28 configure. This causes the collector to be compiled with -D GC_THREADS
29 ensuring thread safety. This assumes use of the pthread_ interface; old-style
30 Solaris threads are no longer supported.
31 Thread-local allocation is now on by default. Parallel marking is on by
32 default starting from GC v7.3 but it could be disabled manually
33 by configure --disable-parallel-mark option.
34
35 It is also essential that gc.h be included in files that call pthread_create,
36 pthread_join, pthread_detach, or dlopen. gc.h macro defines these to also do
37 GC bookkeeping, etc. gc.h must be included with one or both of these macros
38 defined, otherwise these replacements are not visible. A collector built in
39 this way way only be used by programs that are linked with the threads library.
40
41 Since 5.0 alpha5, dlopen disables collection temporarily,
42 unless USE_PROC_FOR_LIBRARIES is defined. In some unlikely cases, this
43 can result in unpleasant heap growth. But it seems better than the
44 race/deadlock issues we had before.
45
46 If threads are used on an X86 processor with malloc redirected to
47 GC_malloc, it is necessary to call GC_INIT explicitly before forking the
48 first thread. (This avoids a deadlock arising from calling GC_thr_init
49 with the allocation lock held.)
50
51 It appears that there is a problem in using gc_cpp.h in conjunction with
52 Solaris threads and Sun's C++ runtime. Apparently the overloaded new operator
53 is invoked by some iostream initialization code before threads are correctly
54 initialized. As a result, call to thr_self() in garbage collector
55 initialization SEGV faults. Currently the only known workaround is to not
56 invoke the garbage collector from a user defined global operator new, or to
57 have it invoke the garbage-collector's allocators only after main has started.
58 (Note that the latter requires a moderately expensive test in operator
59 delete.)
60
61 I encountered "symbol <unknown>: offset .... is non-aligned" errors. These
62 appear to be traceable to the use of the GNU assembler with the Sun linker.
63 The former appears to generate a relocation not understood by the latter.
64 The fix appears to be to use a consistent tool chain. (As a non-Solaris-expert
65 my solution involved hacking the libtool script, but I'm sure you can
66 do something less ugly.)
67
68 Hans-J. Boehm
69 (The above contains my personal opinions, which are probably not shared
70 by anyone else.)