Tried your code on 5.10.1 on Windows, 5.10.0 on Cygwin, 5.8.8 on CentOS all OK. I did reproduce the seg. fault on 5.10.0 on Ubuntu.
(gdb) bt
#0  Perl_do_tell (my_perl=0x9c01008, gv=0x0) at doio.c:1038
#1  0x080fac6a in Perl_pp_tell (my_perl=0x9c01008) at pp_sys.c:2077
#2  0x080b20f9 in Perl_runops_standard (my_perl=0x9c01008) at run.c:38
#3  0x080b0560 in perl_run (my_perl=0x9c01008) at perl.c:2391
#4  0x08063ebd in main (argc=3, argv=0xbfff4dd4, env=0xbfff4de4)
    at perlmain.c:113

[download]

In reply to Re: Perl segfaults: Why? by cdarke
in thread Perl segfaults: Why? by bv

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.