Re: EInvalidOp in D2007 FillChar & Move

John O'Harrow wrote:
From your symptoms, it appears that some other code has left data on the FPU stack, causing it to overflow when FillChar or Move try to use it. Do you have a code snippet with which I can reproduce the symptoms to investigate this further?

I wish. :( The FillChar one has occurred for one user a few times, but it isn't really repeatable, and the Move one has only occurred once so far. The FillChar ones are generally occurring deep in some Indy code:

00403f3a +032 System 281 +0 @FillChar
00407430 +144 System 281 +0 DynArraySetLength
0040747d +005 System 281 +0 @DynArraySetLength
004d7ade +046 IdGlobal 3974 +2 ToBytes
0085139e +03a IdIOHandler 1862 +5 TIdIOHandler.WriteDirect
0085117a +04e IdIOHandler 1767 +5 TIdIOHandler.Write
008505dc +1b4 IdIOHandler 1309 +47 TIdIOHandler.Write
....

I don't think they'll use too much assembly just for portability reasons. Are there any op codes or other things related to the FPU that I can search for to try to narrow it down?

Thanks,
Craig
.