|
in reply to Re: Re: Re: segmentation faults
in thread segmentation faults
Well not very sure about it actually. the thing is that it will parse my doc correctly 1000 times, then segfault. one thing that strikes me now, is that when I use it with no signalling in my script, it parses 100 000 times without a glitch. could be that signalling stuff that makes it segfault, i'm gonna try...
Another thought about it : if it segfaults, then I can trap this signal. if I do, will my script go back to normal or die cause its buggy ? I'm gonna try...
|
Re: Re: Re: Re: Re: segmentation faults
by RMGir (Prior) on Aug 21, 2002 at 16:24 UTC
|
Signals and perl don't mix very well.
In perls < 5.8 (?), your signal could get caught in the middle of an opcode execution, so your signal handler could wind up "reentering" a non-reentrant part of the perl core, like the regex engine.
In perls after 5.8, your signal will be deferred until the current op completes, but it could still interrupt system calls, and not restart them, I believe.
--
Mike | [reply] |
|
