Segmentation Violation

[George Simon]

You say that filePro does a quick cleanup and then exists.  Does that release the license being used?
The problem we are having is that somehow we are exceeding the number of licenses.
If the segmentation violation releases the filePro license then maybe we are not having a segmentation violation.  It could be some other filePro error, I guess, like too many nested gosubs or some index error.

George Simon
American River International
Celebrating Over 28 Years of Success!
908-354-7746 x 103
http://www.americanriverintl.com/

The GREATEST compliment I can receive is a REFERRAL from my customers and friends!

Please visit our website at www.americanriverintl.com for more details & information

Now available on the American River International Website! 
Links to Denied Parties, FDA Web site & Safe Harbor Policy,
also available E-Tracking - our NEW online tracking site. 



-----Original Message-----
From: Kenneth Brody [mailto:kenbrody at spamcop.net] 
Sent: Wednesday, July 21, 2010 12:09 PM
To: George Simon
Cc: filepro-list at lists.celestial.com
Subject: Re: Segmentation Violation

On 7/21/2010 10:41 AM, George Simon wrote:
> I've been asked the following question by one of our programmers that is experiencing difficulties with segmentation violations.
>
> "George,
>
> If you have any information on this, it would be great.  But, could you message the filePro list
> to see if there is a way to exit from a segmentation violation if a process crashes on the cron?
>
> Thanks"
>
> I told him that I did not think so but would post the question here.
[...]

A SEGV means the program has already exited.

Well, to be more specific, in the case of filePro, filePro catches the 
SIGSEGV signal, does some quick cleanup, outputs "***segmentation 
violation", and then exits.

Are you saying this isn't the case on your system?

-- 
Kenneth Brody