VirtualTable in 6.1.4 SDAC : $C0000005 ACCESS_VIOLATION

Discussion of open issues, suggestions and bugs regarding Virtual Data Access Components for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
PaulT2
Posts: 29
Joined: Wed 15 Aug 2007 19:31

VirtualTable in 6.1.4 SDAC : $C0000005 ACCESS_VIOLATION

Post by PaulT2 » Fri 17 Feb 2012 12:27

Using XE2 Pro Update 3 (version 16.0.4358.45540), SDAC 6.1.4 along with FastMM4 in full debug mode for 64 bit, I get error "$C0000005 with message 'c0000005 ACCESS_VIOLATION' " when trying to call VirtualTable.LoadFromStream.

This does not appear to cause a problem in production in either 32bit or 64 bit mode, but only shows itself when using the FullDebugMode of FastMM4 (I also switch on EnableMemoryLeakReporting and CheckHeapForCorruption).

Apart from the FastMM settings, all that is needed to repeat the problem is a default project with a VirtualTable component dropped on it. I then use the following commands :-

Stream := TResourceStream.Create hInstance, 'DatabaseUpdate', Types.RT_RCDATA);

VirtualTable1.IndexFieldNames := 'Major ASC; Minor ASC ; Release ASC ; Step ASC';
VirtualTable1.LoadFromStream(Stream,true);

The ACCESS_VIOLATION appears on the LoadFromStream statement.

Are you able to duplicate this ? I'm actually wondering if this is a problem in the Delphi compiler at this stage.

AlexP
Devart Team
Posts: 5530
Joined: Tue 10 Aug 2010 11:35

Post by AlexP » Mon 20 Feb 2012 09:22

Hello,

Please send a sample with all the FastMM settings demonstrating the problem to Alexp*devart*com

PaulT2
Posts: 29
Joined: Wed 15 Aug 2007 19:31

Post by PaulT2 » Mon 20 Feb 2012 14:35

Hi Alex,

Just confirm, you should have had en email from me earlier today with a sample project attached.

Paul.

AlexP
Devart Team
Posts: 5530
Joined: Tue 10 Aug 2010 11:35

Post by AlexP » Tue 21 Feb 2012 09:52

hello,

I got your message and reproduced the problem under Windows 64.
I'll let you know as soon as we get the results

AlexP
Devart Team
Posts: 5530
Joined: Tue 10 Aug 2010 11:35

Post by AlexP » Tue 21 Feb 2012 12:55

Hello,

We have fixed the problem.
This fix will be included in the next build.

Post Reply