[utf8vcl-general] Some AV problems
Status: Alpha
Brought to you by:
bluelive
From: Sasa Z. <sa...@ma...> - 2007-05-19 11:23:01
|
Hi Bart, This is quite promising project! Congratulations! Realization idea of intercepting API calls is quite effective, except some AV problems in specific situations. The first one is that in some specific situatioins and AV is shown (Write to 0000000) in StdWndProcInerceptW2U on last line ("Result..."). Unfortunately, I'm unable to locate where potential problem starts, since AV is not raised on the same position. Problem are raised on an application I use to copy tables from one ADO source to second one, mostly using variant type. If that information is not enough to locate potential cause of the problem, when free time allow I will try to create and provide test case with an example. Second one is incompatibility with tntware components. AV is rising on the moment of activating form with tntware components. In some specific cases it is very useful to have native UTF-16 component along with regular string components (where strictly ANSI is enough). Third one is AV, raised when FastMM4 is using and should show memory leak report. If it can be possible, suggestion is to create an Enable/DisableUTF8 interceprions procedures, which will help all listed situations. D7 SP1, W2K Pro SP4, all UTF8VCL units are included as very first one in uses of the delphi project (.dpr), except when used FastMM4. Thank you for your time. Sasa -- www.szutils.net |