I have another answer I can live with a little easier. I wrote another
proof of concept script wherein the MainWindow is kept as mentioned before.
It looks like I can create and destroy Toplevel windows as I need to,
while keeping the MainWindow withdrawn.

This works without getting a segmentation fault:

sub service_for_mw_button_press {
  my ($mw) = shift;
  my $top_level = $mw->Toplevel

[download]

and then later, when I no longer need the $top_level,

$top_level->destroy;
undef($top_level);
$mw->deiconify;
$mw_raise;

[download]

This idea, plus a redesign to make the real program an event driven
design from the beginning, should do the job. Thanks for all of your
help.

In reply to Re^2: "Segmentation fault after destroying window" by mnooning
in thread "Segmentation fault after destroying window" by mnooning

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.