Custom Query (80 matches)

There is a bunch of constants (such as IP_ADD_MEMBERSHIP) that were redefined by Microsoft in WinSock2 and have values incompatible with WinSock1. We miss these new defines in Odin headers and simply fall back to old ones.

While it seems to work at binary level (because the values for constants supplied to Odin by the application are taken from the real MS SDK when the application is built and get properly recognized by the new WinSock2 APIs in the Odin code), compiling applications at source level drags the old constants in while actually calling the new WinSock2 APIs and as a result these APIs get wrong parameters and return a failure.

This app runs with an older Odin Build 2010-09-06: Dmitry A. Kuminov

Since 0.8.x releases the static text is missing. Only input fields are shown.

​http://micrometals.com/downloads/MicroRelease_March2010.exe

Size 1,5MB, no installation needed, start with "pe MicroRelease_March2010.exe"

It makes sense to build the whole Odin with the latest GCC 4.x. Among other things such as the overall better quality of the compiler comparing to the ancient VAC3 and the fact that GCC's kLIBC is already widely used in the system (including Odin itself), this has another important advantage: VAC3 runtime (which Odin CRT DLL is currently comprised of) has a limitation that it requires using DosExitList?() in a DLL that uses C++ classes and wants destructors of static/global objects to be properly called at program termination which is very inconvenient and kind of dangerous -- a failure in a DosExitList? routine may turn process into a zombie.

This is especially a problem when Odin CRT DLL is mixed with some other C runtime DLL like kLIBC. kLIBC does all static destruction at DLL termination time but this happens after processing exit list routines and may easily create a situation when a C++ kLIBC class makes a call to Odin (e.g. some Win32 API) which ends up in a C++ Odin class but since Odin CRT is already uninitialized, the application will most likely crash.

BTW, such DosExitList?() usage in Odin and in VAC runtime may be also a reason for the infamous hang in DosExitList? at program termination on SMP machines. Or somehow related to that hang. I don't have any proof so far, just a feeling.