Reply to thread

Message

<blockquote data-quote="JMS" data-source="post: 44376" data-attributes="member: 13261">Hi drak,just a side note (not related to your current post but to the project): triggered by some other discussion in some other forum yesterday I took a short look into the code for your core filter. I recognized that you are using the TTDVBACC.DLL in the current version (which is C++.NET 2003 based) from inside the C++ 2005 code. Did you make sure that all structures / classes you are using fit in size (just to avoid very very hard to detect crashes in the future)? What I mean is: you create (new) a C++ class in C++ 2005 using a C++.NET 2003 header. If in C++ some member of the class is smaller (e.g. CFile, CString, ... - MFC stuff) than for C++.NET 2003 fewer memory will be allocated and memory will get corrupted over time. In some rare situations (inline access to members) even the other way around may produce trouble.In DVB.NET you'll find one class (LegacySizes or so) with all the C++.NET 2003 sizes reported from the compilers sizeof(). You should take a few minutes to get the C++ 2005 values and compare it for those classes you use. In fact getting the same size is not bullet-proof but far along 99% of safeness.Just a hintJochen</blockquote>

[QUOTE="JMS, post: 44376, member: 13261"] Hi drak, just a side note (not related to your current post but to the project): triggered by some other discussion in some other forum yesterday I took a short look into the code for your core filter. I recognized that you are using the TTDVBACC.DLL in the current version (which is C++.NET 2003 based) from inside the C++ 2005 code. Did you make sure that all structures / classes you are using fit in size (just to avoid very very hard to detect crashes in the future)? What I mean is: you create (new) a C++ class in C++ 2005 using a C++.NET 2003 header. If in C++ some member of the class is smaller (e.g. CFile, CString, ... - MFC stuff) than for C++.NET 2003 fewer memory will be allocated and memory will get corrupted over time. In some rare situations (inline access to members) even the other way around may produce trouble. In DVB.NET you'll find one class (LegacySizes or so) with all the C++.NET 2003 sizes reported from the compilers sizeof(). You should take a few minutes to get the C++ 2005 values and compare it for those classes you use. In fact getting the same size is not bullet-proof but far along 99% of safeness. Just a hint Jochen [/QUOTE]

Verification