Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Re: return code 139

by MZSanford (Curate)
on Mar 04, 2002 at 12:25 UTC ( #149099=note: print w/replies, xml ) Need Help??

in reply to return code 139

139 is the system return code to indicate a segmentation violation. I found a few references here and here
from the frivolous to the serious

Replies are listed 'Best First'.
Re: Re: return code 139
by riffraff (Pilgrim) on Mar 04, 2002 at 15:40 UTC
    If the error returned is >128, subtract 128 to get the signal number. 139-128=11, SIGSEGV, segmentation violation.

    The following is from perldoc -f system:

    You can check all the failure possibilities by inspecting `$?' like this:

    $exit_value = $? >> 8; $signal_num = $? & 127; $dumped_core = $? & 128;


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://149099]
[Corion]: Meh. I get the feeling I should post a call-to-action for people to test their modules with the upcoming 5.26 (or 5.25.latest), as it seems that the smoke testers don't really weed out modules that fail without . in @INC
[Corion]: But without instructions on how to easily test things yourself, I don't think such a call to arms is helpful
[Corion]: (this post on / p5p makes it seem to me that smoke testers seem to have a blind spot there)
[Corion]: Hmmm. Maybe setting $ENV{PERL5LIB}=" some path without dot"; perl Makefile.PL; make test already is enough to locally test your module...
[Corion]: Meh, no, will need a BEGIN hook...
[Corion]: ... and PERL5OPT does not like -e in it :-(
[Corion]: Ah. The magic invocation is set PERL5OPT=-M-lib=. (equivalent of no lib '.';
[Corion]: )

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (7)
As of 2017-03-27 08:06 GMT
Find Nodes?
    Voting Booth?
    Should Pluto Get Its Planethood Back?

    Results (317 votes). Check out past polls.