in reply to [SOLVED] Printing an object when you only have the refaddr string for it

That value is a number that makes sense only while the program runs, and be meaningless after. Run the program twice with the same input, and you will almost certainly never see the same value repeated. If you have the source for the module, you might make a local copy with some diagnostic statements added.

Dum Spiro Spero
  • Comment on Re: Printing an object when you only have the refaddr string for it

Replies are listed 'Best First'.
Re^2: Printing an object when you only have the refaddr string for it
by delias_ (Acolyte) on Nov 05, 2015 at 20:24 UTC
    I realize it only exists while the program runs and the address is never the same on subsequent executions, but I will only ever need to access it immediately while it's still in scope anyway. I can dig into the module of course and make the error sub more elaborate to check for data structures within an err message using $@, but that wouldn't be the on-the-fly universal fix I'm attempting to get at.
      ... I will only ever need to access it immediately while it's still in scope ...

      The phrase "... it will error out with a message ..." in the OP suggests that an exception has already been thrown, suggesting in turn that the scope of the object has been exited and the object itself marked for garbage collection. Does the thrown exception carry a copy of the object reference, thereby defeating GC, in addition to a mere stringization thereof? That seems to me to be the only hope you would have of reliably going back to the object in question with the object of dumping it in some useful way.


      Give a man a fish:  <%-{-{-{-<

        That is correct, there is an array reference it carries with the object. nested under $obj-{error}->[ arrayref here with more array refs under it ] while the function $obj->error provides the stringification at $obj->{error}->{message} Verified it's still in scope using Data::TreeDumper which shows the address.

      For your universal version, you need to run the program in an environment that has access to the module's symbol table. It would not surprise me to find out such a thing exists; it's far beyond what I know :)

      2 minutes with Super Search comes up with Devel::SymDump.

      Dum Spiro Spero