Segmentation Violation

[Kenneth Brody]

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