I hope this information additional information helps to solve the problem:

I commented the code like this.
$SIG{'WINCH'} = sub { # if (!$CONNECTED) { # return 1; # } # while (! $EXP -> slave) { # select(undef, undef, undef, 0.25); # }; # $EXP -> slave -> clone_winsize_from(\*STDIN); kill WINCH => $EXP -> pid if $EXP -> pid; };

Then, followed the next steps

test@test-VirtualBox:~$trap 'stty size' winch test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 test@test-VirtualBox:~$ 24 85 <-= DISCONNECTED (PRESS <ENTER> TO RECONNECT) (Thu Nov 28 13:14:40 20 +19)

And then stops

Looks like it enters into an infinite loop. This behaviour is not seen in any other desktop, environment.

In other desktop environments you see:

hans@hans-desktop:~$ trap 'stty size' winch hans@hans-desktop:~$ hans@hans-desktop:~$ hans@hans-desktop:~$ hans@hans-desktop:~$ hans@hans-desktop:~$ hans@hans-desktop:~$

The winch signal is never called when you arrive to the end, only on a window resize.

It would be help full for me to see if I understand the code correctly

$SIG{'WINCH'} = sub { kill WINCH => $EXP -> pid if $EXP -> pid; };

The kill line, what it does is stop the WINCH event from being called again be the same event, right?

Could it be that in xubuntu is not being sent and then the signal keeps arriving until there is a stack overflow or something similar?


In reply to Re: application crash during WINCH Signal by hanspr
in thread application crash during WINCH Signal by hanspr

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.