![]() With the files main.c and foo.c used in the previous example: Symbols can also remain undefined when a symbol reference in a relocatable object is bound to a symbol definition in an implicitly defined shared object. Although thisĮrror can be detected during the initial execution and testing of an application, more complex execution paths can result in this error condition taking much longer to detect, which can be time consuming If an unavailable symbol reference is required during the execution of a process, a fatal runtime relocation error will occur. Take care when using the -z nodefs option. If you want to allow undefined symbols, as in cases like the previous example, then the default fatal error condition can be suppressed by using the link-editor's -z nodefs option. In a similar manner, a symbol reference within a shared object that is never matched to a symbol definition when the shared object is being used to build a dynamic executable, will also result in When the link-editor is generating an executable output file, the link-editor's default behavior is to terminate the link-edit with an appropriate error message should any symbols remain undefined.Ī symbol remains undefined when a symbol reference in a relocatable object is never matched to a symbol definition: The effect of these undefined symbols on the link-edit process can vary according to the type of output file being generated,Īnd possibly the type of symbol. These symbol references are referred to as undefined symbols. ![]() After all input files have been read and all symbol resolution is complete, the link-editor searches the internal symbol table for any symbol references that have not been bound to symbol definitions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |