(5.8 sounds interesting from the time frame. Will check this tomorrow & update this reply node. thx!)

OK/fail*: just setting PERL_SIGNALS=unsafe in the shell indeed does the trick, however this affects the whole program, even if it makes the original program work again.

FAIL: there are low level readline lib variables with interesting names e.g. in Term::ReadLine::Gnu: _rl_vars{rl_catch_signals}=['C',20]; however these reliably fail for me as I'm too lazy to actually read both the library and XS to make sense of them :/.

FAIL: there were some related pointers via google that PERLIO=perlio instead of stdio solves some recent trouble with 5.10 with IO. Changing the environment variable alone is insufficient. And readline might well do it's own IO in parallel to perlio!?

probably OK and localized: Perl::Unsafe::Signals

OK/fail* and localized: POSIX::sigaction, see search.cpan.org/~dapm/perl-5.10.1/pod/perlrun.pod#PERL_SIGNALS and search.cpan.org/~dapm/perl-5.10.1/pod/perlipc.pod#Deferred_Signals_(Safe_Signals) (sorry, the shortcut perlipc and perlrun docs are different, incomplete versions; thus the cpan links instead).

*) "fail" as I cannot see a way to get the partial line on ALARM. For both POSIX::sigaction and also PERL_SIGNALS=unsafe, the original way to access it seems broken.

In reply to Re^3: pmchat-2 by jakobi
in thread pmchat-2 by samwyse

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.