Mail Archives: djgpp/1994/02/16/22:01:38
Mike Castle suggests:
>> The port worked reasonably well; only one example (reload-test) did
>> not work. In debugging the code for this example, I kept getting
>> unresolved references to ctor_list and dtor_list. At the time I
>> was C++ illiterate, but I now suspect that these are
>> contructor/destructor lists. I believe these are linked in from
>> crt0.o. In this example, the entire current program is unlinked,
>> then a new, different program is linked in. This different program
>> is not completely linked (that is, it hasn't been linked with
>> crt0.o) and so these last couple things are missing. Hurm.. I just
>> now thought of it... these *might* be able to be resolved if libc.a
>> is dynamically linked in.... *shrug*
The ctor_list and dtor_list are in fact the lists of constructors
and destructors for global objects (in most implementations of C++
that I know the implementation of). So that's right. On the other
hand I doubt that they'd be in libc.a, because they are a C++
feature. (But what do I know?) Anyway, that's the place to start
looking.
--Steve
- Raw text -