You could try trapping the output using IPC::Open3. I do this for various deparse things, something like this will get the data for you. There is obviously neater ways to handle the data coming in, but for this example it works.

use strict;
use IPC::Open3;  
                                                                      
+                                                                     
+                 
my $debug = open3(\*WRITE, \*READ, \*ERROR, "perl -Mre=debug -e 'qr/..
+./'");

#old incorrect stuff :)
#while (<READ>||<ERROR>) {
#    my (@read, @error) = (<READ>, <ERROR>);
#    print "READ: @read\n";
#    print "ERROR: @error\n";
#}

print <ERROR>;
close(\*WRITE, \*READ, \*ERROR);
[download]

If doing the above is 'naughty' in any way please tell me, I have no idea of the plethora of caveats it possibly entails :)

UPDATE: Thanks diotalevi, I overlooked that. If you take out the while loop and just simply print <ERROR>; it will show what it is meant to for the intended purpose, I had other uses on my mind at the time, one of which was obviously to stuff it up :) Have ammended code as such.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.