Why doesn my protocol woth with NesCT & OMNeT++ even though it compiles to an executable?
This is usually caused by the usage of uninitialized variables. GCC fills all the memory with 0 before starting an application; whereas, MS compilers fill the memory with 0xCD. In this case, your variables will have the value of 0xcd or 0xcdcd depending on the type of variable. The solution for this is not to depend on compiler for variable initializations and do custom initialization inside your init functions. Another strategy would be to assign 0 to all variables you declare. Then, NesCT would also initialize them during class construction.