Bug 11611

GemStone/S

6.7, 6.6.5, 6.6.4, 6.6.3.3, 6.6.3.2, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8, 6.5.7.5, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.2.x, 6.2, 6.1.6, 6.1.5, 6.1.x, 6.0.x, 5.1.5.1, 5.1.5, earlier versions

Unix

Incorrect unresolved external references cause errors at run-time

When you link a GemStone user-action shared library, be aware that  
incorrect unresolved external references can cause run-time errors.  
Due to the way these libraries are set up and used, you must leave  
unresolved external references to GemBuilder for C functions in the  
finished library.  These references are resolved when the user-action  
library is loaded by GemStone.  However, if you misspell a GemBuilder  
for C function call,  you may not discover it until run-time, when  
your process terminates with an unresolved external reference error.

Workaround

Use a compiler that returns warnings for undeclared functions.


Last updated: