There is only one truly portable and robust way to do that: redirect STDERR to a temporal file before calling into XS and read it afterwards. 
# Untested. Note also that this code will not handle special
# cases as STDERR being closed, tied or attached to a file
# descriptor different than 2.

use autodie;
use File::Temp qw(tempfile);

open my $olderr, '>&STDERR'; # save STDERR
my $fh = tempfile();
open STDERR, '>&', $fh;

my $entry = Text::BibTeX::Entry->new($bib_entry);
open STDERR, '>&', $olderr; # flush and reset STDERR

seek($fh, 0, 0);
my $err = do { local $/; <$fh> };
close $fh;

[download]

In reply to Re: STDERR going to string by salva
in thread STDERR going to string by philkime

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.