RADE

Multi-Workspace Application Builder

Frequently Asked Questions

Find answers to usual questions regarding mkmk family tools

Quick Reference

Abstract

This article gathers answers to usual problems one user may encounter when using mkmk and related commands. Answers are grouped by topics listed below.


Warnings Issued by Underlying Compilers and Linkers

Warning on VC60.pdb on Windows

The following warning is often issued:

Creating library E:\TESTB12\.\intel_a\code\bin\CAADrwCreateDim.lib and object E:\TESTB12\.\intel_a\code\bin\CAADrwCreateDim.exp SystemUUID.lib(CATIUnknownList.obj) : warning LNK4099: PDB "vc60.pdb" was not found with "E:\CATIAB12\.\intel_a\code\lib\SystemUUID.lib" or at "E:\TESTB12\intel_a\code\bin\vc60.pdb"; linking object as if no debug info

It is due to the fact that some archives only contain UUID definitions which confuses the windows link-editor.

This warning can be safely ignored.

[Top]

Why Should I Avoid Unloading and Loading Modules?

Unloading a DLL while CATIA is running, and then reloading it is technically possible thanks to some system calls. Nevertheless, this may lead to unpredictable results such as memory corruptions, memory leaks, or even process crashes. This may happen because the unloaded DLL is reloaded at a different memory address. All the dynamic bindings set, for example, through QueryInterface, before the DLL unload and that might be held by objects in the other DLLs will now point to invalid addresses where no DLL is mapped any longer. When these objects are used, the application cannot thus behave as expected.


History

Version: 1 [Dec 2003] Document created
[Top]

Copyright © 2003, Dassault Systèmes. All rights reserved.