I don't see why breakpoints would be attached to machine opcodes or addresses. Perl code runs in a virtual machine of sorts, so they would be attached to Perl opcodes or lines. (Yes, line information is available. It's stored in nextstate ops for warnings and die.) Sorry, I don't know any details beyond that.

Example Perl opcodes: 

$ perl -MO=Concise,-exec -e'
   print "Hello, ";
   print "World!\n";
'
1  <0> enter
2  <;> nextstate(main 1 -e:2) v:{
3  <0> pushmark s
4  <$> const(PV "Hello, ") s
5  <@> print vK
6  <;> nextstate(main 1 -e:3) v:{
7  <0> pushmark s
8  <$> const(PV "World!\n") s
9  <@> print vK
a  <@> leave[1 ref] vKP/REFC
-e syntax OK

[download]

In reply to Re: How perl debugger breakpoint works? by ikegami
in thread How perl debugger breakpoint works? by PerlOnTheWay

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.