Bug#665388: libperlbal-xs-httpheaders-perl: FTBFS: C code doesn't load reliably

[Aaron M. Ucko]

Source: libperlbal-xs-httpheaders-perl
Version: 0.20-1
Severity: serious
Justification: fails to build from source

Builds of libperlbal-xs-httpheaders-perl have failed on several
architectures with errors of the form

  #   Failed test 'use Perlbal::XS::HTTPHeaders;'
  #   at t/HTTPHeaders.t line 10.
  #     Tried to use 'Perlbal::XS::HTTPHeaders'.
  #     Error:  Not a CODE reference at /usr/lib/perl/5.14/DynaLoader.pm line 207.
  # END failed--call queue aborted at .../libperlbal-xs-httpheaders-perl-0.20/blib/lib/Perlbal/XS/HTTPHeaders.pm line 207.
  # Compilation failed in require at (eval 4) line 2.
  # BEGIN failed--compilation aborted at (eval 4) line 2.
  Bizarre copy of UNKNOWN in list assignment at /usr/share/perl/5.14/Test/Builder.pm line 942.
  Attempt to free unreferenced scalar: SV 0x9fd9500, Perl interpreter: 0x9fd9008 at /usr/share/perl/5.14/Test/Builder.pm line 942.
  # Looks like you planned 40 tests but ran 6.
  # Looks like you failed 1 test of 6 run.
  # Looks like your test exited with 255 just after 6.
  t/HTTPHeaders.t .. 
  Dubious, test returned 255 (wstat 65280, 0xff00)
  Failed 35/40 subtests 

There's no obvious pattern to the set of architectures on which the
test fails, which includes (linux-)i386 and kfreebsd-amd64 but not
(linux-)amd64, hurd-i386, or kfreebsd-i386, so I suspect that some
sort of random factor may be involved; perhaps the C code isn't
properly initializing some memory contents.  (If so, valgrind may be
able to help catch the problem.)

Could you please take a look?

Thanks!