On 23/05/2011 08:47, Alex Peshkoff wrote: > On 05/23/11 14:36, Adriano dos Santos Fernandes wrote: >> On 23/05/2011 03:39, Alex Peshkoff wrote: >>> On 05/22/11 19:02, Adriano dos Santos Fernandes wrote: >>>> Hi! >>>> >>>> This method caches created vtable in a map using original vtable address >>>> as the key. >>>> >>>> When libraries are unloaded, two problems happen: >>>> >>>> 1) Memory leaks. >>>> 2) This is even serious, as may get the system to crash in normal usage. >>>> New libraries are loaded and may reuse the address space of the unloaded >>>> one. Now the vtable cache becomes totally incoherent. >>> Well known to me issue. Did not give it high enough priority cause this >>> branch is never used and will not be used in FB3. >>> But certainly will fix a least before beta1. >>> >> What do you mean by "this branch is never used and will not be used in FB3"? > Something can be upgraded only in a case when there are older versions. > Taking into an account that FB3 will be the first version, working with > interfaces, it will never need to upgrade something. > The version scheme must be know to work since initial version, cause then nothing could be changed later.
The code being writing now should better take into account it. It will be much more difficult to add version verification later to existing code. So instead of removing then, we should add then to each place where interactions of objects of different modules happen. Adriano ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
