Seg Violation on Linux

[John Esak]

>
> There is no lookup dash involved.  One record in the current file, then
> I call table 1, call table 2, call table 3 (as many as 40 times) and/or
> call table 4 as many as 100 times.  (It is strange but the ones I was
> having the most trouble with were not the ones with the most calls, it
> was one with 9 and one with 20 calls.  So I could not say that the more
> I activated the call of table 3 the more likely it was to crash.)
>
> Table 3 was where the crash was happening for the longest time.  After
> some adjustements (shrunk some arrays, shrunk some declared variables,
> etc.) I somehow got it to happen after all the calls were finished and
> when the last command was executed (EXIT).
>
> I had a suggestion to get the 5.0.14 version and I did that install this
> morning on my test system.  That actually seems to have fixed the
> problem (cross my fingers) on the most part.  I tried to process my test
> sets and only one crashed (Back in Call table 3 after only 5 calls).  So
> I am almost there.
>
> I have more testing to do to make sure all is solid but I delayed
> installation on the customer system until I got some resolution on this
> issue.  These are run to load data files received and if it hangs will
> be a real problem.  I wanted to be satisfied that I had done everything
> possible to stabilize the logic.
>
> In my early tests, I did determine that some issues were caused by
> special case stuff for reading and processing the file.  But I have that
> all great now.
>
> I will continue to test, but I am real close.  If I discover anything
> that could be reported as a bug, I will let you know.  This kind of
> error can be hard to pin down.
>
>
>
> Nancy
>
> >
> > --
> > KenBrody at BestWeb dot net        spamtrap:
> <g8ymh8uf001 at sneakemail.com>
> > http://www.hvcomputer.com
> > http://www.fileProPlus.com
> >
> >
>
>
> --
> Nancy Palmquist 		MOS & filePro Training Available
> Virtual Software Systems	Web Based Training and Consulting
> PHONE: (412) 835-9417		   Web site:  http://www.vss3.com
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list

Just a thought. Since you are doing so many iterative CALL's. (Ken may say
this won't help or will do nothing of any impact...) but, how about CALL'ing
a completely blank table in-between every subsequent CALL from the INPUT
table. I mean the special blank CALL has nothing on it but an END statement.
Then, call the proper CALL table. This shouldn't hurt anything, but it might
do something good with memory and re-allocation of it.

John