Re^4: using perldb (neither 'b compile' nor 'b postpone' seem to work)

[LanX]

Thanks for your feedback.

I now have the impressions that the b compile breaks actually work, they just stop at the point of compilation (sic) not execution.

I can actually see that postponed breaks are translated to breaks listed with 'L', at least when giving full qualified subnames. They are just not breaking ...

What's making it weirder is that those commands seem to interfere with each other, so I should better untangle the test cases...

[LanX]

I'm still testing and didn't come to a conclusion why it's broken, but I wanted to give a feedback now:

b postpone PKG::SUBNAME is definitely translated into b SUBNAME after a require or use . Inspecting the breakpoints with L shows exactly the same effect like a manual b SUBNAME after the require.

Difference is that the former just don't break. (???)

I'll try to generate an automated test, probably someone can run it via perlbrew on different versions. (I need a way to direct the output into a parsable variable)

I'll also try to look into the internal DB::data-structures of perl5db.pl

[karlgoethebier]

« I'll try to generate an automated test, probably someone can run it via perlbrew on different versions.»

Why not.

1. Post which versions you want
2. Post the automated test(s)
3. I’ll run it/them
4. Feel free to correct me if I’m wrong

As I tested some of BUK‘s stuff I see no reason why I shouldn’t do that for you. As it is for the good cause.