From: Kai T. <kti...@go...> - 2012-08-01 05:36:56
|
2012/7/31 Ozkan Sezer <se...@gm...>: > On 7/31/12, Kai Tietz <kti...@go...> wrote: >> Hi Ozkan, > [...] >> So, to avoid such issues in future I begun to abstract secure-API in >> our runtime. See revision 5290 as a start. Important here is that >> for msvcrt.dll we have to remove the secured-API > > Was marking the msvcrt.dll exports as DATA not our policy > in these kinds of situations? > >> and remove the >> _CRTIMP from the header-definition, as soon as we have a forwarder >> (and or emulation) function in secapi/ folder. >> >> Regards, >> Kai > > -- > O.S. Well, not in this case. We mark it as DATA, if we are overriding functionality, but we can be sure that import is present. Here we have to deal with the issue that import-function might not be present in msvcrt, so we need to remove it from msvcrt's import library and deal with the _imp-symbol ourself. Kai |