Your message dated Thu, 3 Nov 2005 13:35:56 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337206: Subject: libdbd-mysql-perl: Machine with latest 
mysql security update segfaults, rebuild needed?
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(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 submit) by bugs.debian.org; 3 Nov 2005 09:32:53 +0000
>From [EMAIL PROTECTED] Thu Nov 03 01:32:53 2005
Return-path: <[EMAIL PROTECTED]>
Received: from sam.opera.com [193.69.113.81] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EXbSn-00042n-00; Thu, 03 Nov 2005 01:32:53 -0800
Received: from rabbit.opera.com (pat.opera.com [193.69.113.22])
        by sam.opera.com (8.12.3/8.12.3/Debian-7.1) with ESMTP id jA39Wo98003433
        for <[EMAIL PROTECTED]>; Thu, 3 Nov 2005 09:32:50 GMT
From: Kjetil Kjernsmo <[EMAIL PROTECTED]>
Organization: Opera Software ASA
To: [EMAIL PROTECTED]
Subject: Subject: libdbd-mysql-perl: Machine with latest mysql security update 
segfaults, rebuild needed?
Date: Thu, 3 Nov 2005 10:32:21 +0100
User-Agent: KMail/1.7.2
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[EMAIL PROTECTED]>
X-Scanned-By: MIMEDefang 2.39
Delivered-To: [EMAIL PROTECTED]
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-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: libdbd-mysql-perl
Version: 2.9006-1
Severity: grave
Justification: causes non-serious data loss

*** Please type your report below this line ***
I have a relatively simple script that segfaults on a machine that has
the latest security updates for sarge, but runs fine on a machine that
has not yet applied them. 

There is an strace at http://rafb.net/paste/results/68YHWC13.html

I took it to #debian-devel, and...:
ruoso   If one security update touched a library which is used by the
Perl XS module... then this can be the cause of the problem     
KjetilK hmmm    
ruoso   aparently, this is what's happening...  
ruoso   libdbd-mysql-perl should be rebuilt     
KjetilK guess so...     
ruoso   KjetilK, can you send a bug report on it?       
KjetilK Sure

So, here we go! 

I used reportbug to submit it, and it looked like it was sent, but 
apparently not...

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages libdbd-mysql-perl depends on:
ii  libc6                  2.3.2.ds1-22      GNU C Library: Shared 
ii  libdbi-perl            1.46-6            Perl5 database interface by 
ii  libmysqlclient12       4.0.24-10sarge1   mysql database client 
ii  perl                   5.8.4-8           Larry Wall's Practical 
ii  perl-base [perlapi-5.8 5.8.4-8           The Pathologically Eclectic 
ii  zlib1g                 1:1.2.2-4.sarge.2 compression library 

-- no debconf information

---------------------------------------
Received: (at 337206-close) by bugs.debian.org; 3 Nov 2005 12:36:33 +0000
>From [EMAIL PROTECTED] Thu Nov 03 04:36:33 2005
Return-path: <[EMAIL PROTECTED]>
Received: from sam.opera.com [193.69.113.81] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EXeKW-0005Pp-00; Thu, 03 Nov 2005 04:36:32 -0800
Received: from rabbit.opera.com (pat.opera.com [193.69.113.22])
        by sam.opera.com (8.12.3/8.12.3/Debian-7.1) with ESMTP id 
jA3CaQ98019910;
        Thu, 3 Nov 2005 12:36:27 GMT
From: Kjetil Kjernsmo <[EMAIL PROTECTED]>
Organization: Opera Software ASA
To: Steve Langasek <[EMAIL PROTECTED]>
Subject: Re: Bug#337206: Subject: libdbd-mysql-perl: Machine with latest mysql 
security update segfaults, rebuild needed?
Date: Thu, 3 Nov 2005 13:35:56 +0100
User-Agent: KMail/1.7.2
Cc: [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[EMAIL PROTECTED]>
X-Scanned-By: MIMEDefang 2.39
Delivered-To: [EMAIL PROTECTED]
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-Level: 
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_01,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

On Thursday 03 November 2005 12:05, Steve Langasek wrote:
> But anyway, as discussed on IRC, it'd really be good to confirm that
> this bug does *not* manifest on the same system when using the
> pre-security-update version of libmysqlclient12.

Right, and it was reproducible with the pre-security build. 

What turned out, upon closer inspection, was that I have an unofficial 
build of librdf-perl (since this is very much a moving target), and 
this uses libmysqlclient14, whereas libdbd-mysql-perl uses 
libmysqlclient12. 

Now, I'm using these in the same script. They both go well on their own, 
but not together... 

So, that's why a manual rebuild of DBD::mysql from CPAN fixed the 
problem: It probably simply used the former library.

I guess this closes the bug, and sorry for the interruption. But at 
least I did ask before filing the bug... :-) Thanks to the fine folks 
of #debian-devel

Cheers,

Kjetil


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

Reply via email to