in continuation of Re^3: how to set a breakpoint by a code reference

It's not a bug-fix but a temporary hack!

put the following line into a file in your homedir called '.perldb'

$DB::alias{b} = q# s/^b\s+(\$\w+)\s*$/'"b ". DB::CvGV_name('.$1.')'/ee
+; #

[download]

it creates an alias which intercepts the debuger command b and tries to replace the code-ref with the ANON-name before calling the real command b.

Works for me!

HTH! =)

Could someone with the newest version of the debugger plz check if the bug is still present and if it can be fixed this way?

update

Well at least the version on cpan seems still to be buggy.

Cheers Rolf

( addicted to the Perl Programming Language)

NB: the Variablename parsing is simplistic things like '::' or _ won't match.

In reply to Re: how to set a breakpoint by a code reference (workaround) by LanX
in thread how to set a breakpoint by a code reference by Matq

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.