Hey all,
Quick question... are there any known issues with reading an writing lots of ansistring in a record to and from a text file? Reason for the question is because I am trying to do just that... but for some reason after it makes a certain amount of reads and writes it gives me some majorly corrupt memory and gives me a runtime error 216 (GPF)

My first thought was that it was my fault (lots of lines of code in this unit) so i went through it with a fine-tooth comb and every single file i opened is closed, every pointer i allocate is freed, etc. The only thing is, since an Ansistring is a pointer... how do I free that memory? Because none of the pointer routines seem to work on them. (Gives me type mismatches)

Oh yeah.. i also went and downloaded the latest snapshot (1.1) and still no luck.

Any ideas?

TIA - Matt

Hey all, Quick question... are there any known issues with reading an writing lots of

ansistring
in a record to and from a text file? Reason for the question is because I am trying to do just that... but for some reason after it makes a certain amount of reads and writes it gives me some majorly corrupt memory and gives me a runtime error 216 (GPF)

My first thought was that it was my fault (lots of lines of code in this unit) so i went

through it with a fine-tooth comb and every single file i opened is closed, every pointer i allocate is freed, etc. The only thing is, since an Ansistring is a pointer... how do I free that memory? Because none of the pointer routines seem to work on them. (Gives me type mismatches)

You can free the memory by assigning an empty string "ansistring:='';"

Oh yeah.. i also went and downloaded the latest snapshot (1.1) and still no luck. Any ideas?

Maybe when you can isolate the problem and mail the required code we can test things. But only from a description that there are possible memoryleaks with ansistrings we can't give any reasonable ideas.

Sebastian Guenther reported something similar.

no I have some problems with failing file handle reads or writes, but no memory corruption actually...

- Sebastian

Sebastian Guenther reported something similar.

Can you send me some source code, then I will try to debug it; Probably there is still some conversion error floating around somewhere in the system unit ?

This will need some debugging, so some code that shows the problem would be nice. Just writing a lot of output to the screen works fine here.

Michael.

normally yes, but in my case it's always the same crash position. (and this is the reason for the error code extension - because I want to know why exactly a read or write access failed.)

- Sebastian

The former may be the first visible consequence of the latter; When memory corruption occurs this does not necessarily result in a access violation/segmentation fault.

Michael.

Hello,
my experience with amount of ansistring:

my unit for CSV databases (simple databases,better tables) works fine on 1.0.2 compiler. It can read 62000 lines from text file and split each line to 6 cells. It stores values in dynamically build structure of records, containing ansistrings and pointers. No problem with it.
I didn't try it with the 1.0.4 compiler.

Most errors "216" in this unit I obtained by my own mistakes. In some cases I miss the inicialization, sometimes bad reference. In that huge code it was very hard to find the error :-)

With best regards
Martin H.