Re^3: How can I turn an op address into the right kind of B::OP?


P is for Practical
	PerlMonks

Re^3: How can I turn an op address into the right kind of B::OP?

by haukex (Archbishop)

on Jul 17, 2018 at 11:58 UTC ( [id://1218650]=note: print w/replies, xml )

Need Help??

in reply to Re^2: How can I turn an op address into the right kind of B::OP?
in thread How can I turn an op address into the right kind of B::OP?

So right now see StackOverflow for this if this question is as confusing to you as appearently it was (is?) to Mike Schwern.

I'm not an expert on the internals, so I just don't have an answer to your question in this case (at least not yet, maybe someday ;-) ). Also, I'm not sure what your use case is, that is, I can't judge if this might be an XY Problem or not.

Comment on Re^3: How can I turn an op address into the right kind of B::OP? Download Code

Replies are listed 'Best First'.

Re^4: How can I turn an op address into the right kind of B::OP?
by rockyb (Scribe) on Jul 17, 2018 at 12:16 UTC

Use case: Devel::Trepan currently reports offsets when it is stopped. It gets this from Devel::Callstack currently. However in the past it didn't, although I can't remember the details, other than it was by some other means as an undocumented feature (which means it is not guarenteed to work in the future).

More generally, if the full OP were available, more information could be gleaned about where Perl is at any given time. It also might be used as a way in decompilation to walk around the point of interest rather than starting from the top and decompiling everything.

I'll be giving a talk on this at Glasgow YAPC 2018, so come see me there for more information. ;-)

[reply]

In Section Seekers of Perl Wisdom