[email protected]
[Top] [All Lists]

Bug#343656: marked as forwarded (libyaml-perl: Bug in "load" OO method)

Subject: Bug#343656: marked as forwarded libyaml-perl: Bug in "load" OO method
From: Debian Bug Tracking System
Date: Tue, 20 Dec 2005 07:03:30 -0800
Your message dated Tue, 20 Dec 2005 16:30:53 +0100
with message-id <[email protected]>
has caused the Debian Bug report #343656,
regarding libyaml-perl: Bug in "load" OO method
to be marked as having been forwarded to the upstream software
author(s) [email protected], [email protected], 
[email protected]

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Received: (at 343656-forwarded) by bugs.debian.org; 20 Dec 2005 14:53:35 +0000
>From [email protected] Tue Dec 20 06:53:35 2005
Return-path: <[email protected]>
Received: from fry.debianforum.de ([] helo=mail.debianforum.de)
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1Eoirv-0007Wu-8c; Tue, 20 Dec 2005 06:53:35 -0800
Received: from localhost (localhost [])
        by mail.debianforum.de (Postfix) with ESMTP id 18313B1C08C;
        Tue, 20 Dec 2005 15:53:34 +0100 (CET)
Received: from mail.debianforum.de ([])
        by localhost (mail.debianforum.de []) (amavisd-new, port 10024)
        with ESMTP id 08393-02; Tue, 20 Dec 2005 15:53:28 +0100 (CET)
Received: from wall.foobar.lan (p54B4852F.dip0.t-ipconnect.de [])
        (using TLSv1 with cipher AES256-SHA (256/256 bits))
        (No client certificate requested)
        by mail.debianforum.de (Postfix) with ESMTP id 26DEBB1C046;
        Tue, 20 Dec 2005 15:53:28 +0100 (CET)
Received: from florian by wall.foobar.lan with local (Exim 4.50)
        id 1EojS2-00066h-EB; Tue, 20 Dec 2005 16:30:54 +0100
Date: Tue, 20 Dec 2005 16:30:53 +0100
From: Florian Ragwitz <[email protected]>
To: [email protected], [email protected],
        [email protected]
Subject: [[email protected]: Bug#343656: libyaml-perl: Bug in "load" 
OO method]
Message-ID: <[email protected]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="XMCwj5IQnwKtuyBG"
Content-Disposition: inline
Priority: normal
X-Operating-System: Debian GNU/Linux 2.6.7-1-686
X-Binford: 5100 (more power)
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at debianforum.de
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-11.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
        HAS_PACKAGE autolearn=ham version=2.60-bugs.debian.org_2005_01_02

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello ingy,

I'm the new Debian maintainer of YAML.pm and just received this bug
report from one of our users. Currently I don't have the time to take a
closer look at it. Maybe you can give a try?


----- Forwarded message from Gilles <[email protected]> -----

=46rom: Gilles <[email protected]>
Reply-To: Gilles <[email protected]>, [email protected]
To: Debian Bug Tracking System <[email protected]>
Subject: Bug#343656: libyaml-perl: Bug in "load" OO method
Date: Fri, 16 Dec 2005 23:57:55 +0100
X-Operating-System: Tiny Tux
User-Agent: Mutt/1.5.11
X-Spam-Status: No, score=3D-1.3 required=3D5.0 tests=3DBAYES_00,
        DATE_IN_FUTURE_06_12 autolearn=3Dno version=3D3.0.2

Package: libyaml-perl
Version: 0.39-1
Severity: important


You'll find here attached 3 files providing a stripped-down version
of a program that uncovered some strange behaviour of the YAML module
when using the "load" method.
In "TY.pm", when using the "Load" function (commented out line), the
behaviour is as expected, but not so with "load" for which the script
The input is correctly read from file, as you can see:

--- !perl/TY
key: some value

Something wrong happens in the "load" OO method:
Use of uninitialized value in substitution (s///) at /usr/share/perl5/YAML.=
pm line 670.
Use of uninitialized value in substitution (s///) at /usr/share/perl5/YAML.=
pm line 671.
Use of uninitialized value in pattern match (m//) at /usr/share/perl5/YAML.=
pm line 673.
Use of uninitialized value in length at /usr/share/perl5/YAML.pm line 675.
Use of uninitialized value in split at /usr/share/perl5/YAML.pm line 678.
And the "dump" shows that the input was not correctly loaded:

--- !perl/TY
key: ~


In the full program I was working on, the side-effect was even stranger: I =
get any of the above error messages from inside YAML.pm *but* on return fro=
m the
"load" method, my variable didn't contain the unserialized "TY" object but =
enclosing data (the equivalent of "$config" in the script provided here)!
[Obviously that doesn't happen with the reduced script, but why, I don't kn=


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-vs2.1.0-rc5+g3
Locale: LANG=3DC, LC_CTYPE=3DC (charmap=3DANSI_X3.4-1968)

Versions of packages libyaml-perl depends on:
ii  perl                          5.8.7-7    Larry Wall's Practical Extract=

libyaml-perl recommends no packages.

-- no debconf information

--- !perl/TY
key: some value

----- End forwarded message -----

Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

Version: GnuPG v1.4.1 (GNU/Linux)



To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

<Prev in Thread] Current Thread [Next in Thread>
  • Bug#343656: marked as forwarded (libyaml-perl: Bug in "load" OO method), Debian Bug Tracking System <=