Some of what you say I can agree with. But "they only exist within a lexical scope"---and why's that? It's because lexical variables cannot access the symbol table. That's why I mentioned that there's a control "sandboxed" way from the debugger. Package variables can be accessed via the symbol table.

As for my $a getting optimized away, I disagree with that because I just don't see how it can be optimized away when it's uninitialized in the subroutine. Here's a little test that I ran:

#!/usr/bin/perl use strict; use warnings; print mt2(55), "\n"; my $a = 23; sub mt2 { my $b = $_[0] * 2; return $a + $b; }
Here's the corrected script:
#!/usr/bin/perl use strict; use warnings; print mt2(55), "\n"; sub mt2 { my $a = 23; my $b = $_[0] * 2; return $a + $b; }
This one works in the debugger. Thanks for the input.

In reply to Re^3: Debugger and lexicals by Khen1950fx
in thread Debugger and lexicals by lzipin

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.