forum.vdsworld.com

webdaddy · Posted: Sat Oct 29, 2005 6:32 pm Post subject: Another Error - Annoying

I keep finding errors in VDS because im it more and more. Now today I found a doozy of an error that makes no sense to me. It started with the dreaded error 217 which appears to be a bug in delphi itself or related to permission problems. Now im getting the following.

I cant believe that these issues would not have been resolved in this version. It just doesnt make sense.

vdsalchemist · Posted: Sat Oct 29, 2005 6:55 pm Post subject:

Webdaddy,
Is that line number correct (ie... 2292769)? What is your program doing at that line? It seems unreal. How big is your program?

webdaddy · Posted: Sat Oct 29, 2005 11:50 pm Post subject: Ha

No my program is not that large. However this is not the first time I have seen this. This is the 4th of 5th time I have run accross this. My program is only 1200 lines of code but it gives crazy errors like this.

I did change the DLL I was using from vdsipp to vdstcp and it fixed the problem. I am not sure what the heck was going on with it.

I wish I had the endurance to code something as large as that... Very Happy

Serge · Posted: Sun Oct 30, 2005 1:39 am Post subject:

my experience tells me that the problem is with the dll in that it is not coping with the data you are feeding it

i suggest that you check all the data you are sending to the dll to make sure that it is what the author of the dll said you should use ie. the right sort of data and in the right format

also, watch out for null entries given to the dll ... it may be that it always wants valid data sent to it

serge

webdaddy · Posted: Sun Oct 30, 2005 3:12 am Post subject: Yep

Well the DLL could'nt handle the amount of data being sent to it. I do check to make sure the data im sending to the DLL doesnt have any null characters. Aparently however if the server got backed up due to alot of events it appended the data being sent later or something similar giving the long line number error message. Application is working now so its all good. I am happy now that I figured out.

webdaddy · Posted: Tue Nov 01, 2005 5:18 am Post subject: Resolved - I dont know why though

In regard to this issue it has been resolved. By putting a wait statement in with 0.1 as the value making the script pause for a tenth of a second it seems to have fixed the error. This is not the first time I have seen this but it doesnt make much sense. Its almost like the informatoin being sent to the DLL was appended ot the information sent right before it which is not in the correct format since it was actually 2 dll messages instead of 1 which caused it to give this weird error. I can reproduce it but dont know exactly why it did it. If you see a very large error line number its worth trying I guess.

Serge · Posted: Tue Nov 01, 2005 5:48 am Post subject:

i have had to add wait statements too ... in mycase it was to parts of a script that saved a file to a hard disk ... to allow for slow hard disk, i found that adding WAIT really did the trick

good to see you resolved the issue

serge

vdsalchemist · Posted: Thu Nov 10, 2005 1:54 am Post subject:

WebDaddy,
If you had to put a Wait statement in your script this is usually a indication that there is a Threading issue with the DLL. Usually you see these errors when using functions that require IO to be Asyncronous. It's very hard to get Multi-threading working with VDS since it is single threaded. Well at least I have had a hard time since I write my DLL's in pure C. The hardest part about being a VDS DLL programmer is the fact that we know nothing about the innerworkings of the VDS runtime. Building Multi-Threaded DLL's in VDS is like trying to balance an ant and an elephant on a tooth-pic using a ping-pong ball as the falcrom Laughing

Well just to let you know it has been my experience that using the wait command is only a bandaid. If the program will be used on other computers then the threads should really be looked at by the author of the DLL.

webdaddy · Posted: Thu Nov 10, 2005 2:40 am Post subject: Oh wow

Well this is happening in VDSIPP and VDSTCP50 (I tried both and had similar results). I have it working but I too would like to see what is causing the problem. Or at least get to the root of it. I am looking at the source code in VDSIPP now to see if I can modify it for my needs.