***segmentation violation

[Bruce Easton]

Walter Vaughan wrote Monday, August 13, 2007 8:26 PM:
[..]
> [export] gave me a ***segmentation violation
[..]
> Finally realized that with that specific file if I create a 
> processing-only 
> table it will segfault. Even with no processing table.
> 
> We're not talking rocket science fpCode either for testing purposes
> 1  -------
>       ¦ If:
>       Then: fn="/tmp/catpipe"
> 2  -------
>       ¦ If:
>       Then: export ascii ofb=(fn) r=\n f=|
> 3  -------
>       ¦ If:
>       Then: ofb(1)=1
> 4  -------
>       ¦ If:
>       Then: ofb(2)=2
> 5  -------
>       ¦ If:
>       Then: ofb(3)=3
> 
> Okay, its running on a AMD64-FreeBSD-6.2 os, and filePro is 32bit 
> compiled for 
> 4.X

[..]

> But okay. Fire up a 32 bit 6.1 FreeBSD box. Same thing. Check 
> permissions till 
> I'm blue in the face.
> 
> Hours now have passed, and it's Monday mid morning. Try on a very 
> old SCO OSR5 
> fp4.5.X box. Code works. Duh. It should have all along. Move code 
> to FreeBSD 
> box. Same segmentation violation. Grr.
> 
[..]

Hmm - Walter - you mention above that the seg. vio. occurs with 
a processing-only format.  Does it not occur on that file with 
some other type of format or are there no other formats?

I seems with testing on all these different platforms that it 
would be unlikely that the segments truely have been violated,
but you moved only the prc table from one system to the 
other, not the whole file, right?

> we decide to 
> leverage an existing export that creates similar data.
> 
> Here's where it gets weirder. At the end of it's table I create 
> an @once area 
> and pop down code. Setup loop and write it as a lookup/export 
> thing. But I gotta 
> flush export after every getnext lookup, so I used something.

Whaddya use here, Walter - Grecian Formula, WD-40? :)  
   
> Segmentation 
> violation.

Yeah - and the Beach Boys only know if this seg. vio. is related 
to one you were getting in the main section. 

> How could that be? Changed it to write export_alias. Works. :)
> 
[..]

> When I added in about 
> 30 lines of (and 
> 20 more exports values) you could then feel it for just a second

yeah, my cell phone does that to me occasionally :) 

> then it 
> continued as normal at about 3k per screen update.
> 
> Forgetting about the seg_vio's, it got me thinking. Is it that 
> more effective 
> when doing exports to stand in a third file and just write your 
> changes in a 
> loop, than when you export per record the "normal way"?  In this 
> case it's about 
> 10 times faster.

Do you mean by using export elsewhere, or by using clerk/report 
with file I/O functions?
 
> 
> ==
> Walter
> 
[..]

Bruce

Bruce Easton
STN, Inc.