Hello Aurelien,
Thank you for giving attention to my bug report.
I don't know the details of how Debian works, so I would be happy if you
could clarify something for me.
We agree that the present bug apparently exists in version 2.7 in glibc
(which is the default version present in Lenny), and is fixed in 2.9
(used in unstable and testing Debian releases).
So, there is a known bug in a core package in the latest stable release
of Debian, and it won't be fixed? Is this the Debian policy? I imagined
that bugs would be fixed in the stable version. What determines which
bugs are fixed in the stable version? Is there a list of known bugs in
the stable version which won't be fixed?
Thanks,
Erland
Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the libc6 package:
#583577: libc6: pthread_mutex_timedlock can segfault
It has been closed by Aurelien Jarno <aurel...@aurel32.net>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Aurelien Jarno
<aurel...@aurel32.net> by
replying to this email.
------------------------------------------------------------------------
Subject:
Re: Bug#583577: libc6: pthread_mutex_timedlock can segfault
From:
Aurelien Jarno <aurel...@aurel32.net>
Date:
Sun, 30 May 2010 11:52:43 +0200
To:
583577-d...@bugs.debian.org
To:
583577-d...@bugs.debian.org
Received:
(at 583577-done) by bugs.debian.org; 30 May 2010 09:52:49 +0000
X-Spam-Checker-Version:
SpamAssassin 3.2.5-bugs.debian.org_2005_01_02 (2008-06-10) on
busoni.debian.org
X-Spam-Bayes:
score:0.0000 Tokens: new, 10; hammy, 115; neutral, 34; spammy, 4.
spammytokens:0.998-1--Lewin, 0.998-1--lewin, 0.993-1--erland,
0.993-1--Erland hammytokens:0.000-+--1024D, 0.000-+--libc6,
0.000-+--Severity, 0.000-+--segfault, 0.000-+--aurelien
X-Spam-Status:
No, score=-5.9 required=4.0 tests=AWL,BAYES_00,HAS_BUG_NUMBER,
URIBL_CNKR,VERSION autolearn=ham version=3.2.5-bugs.debian.org_2005_01_02
Return-path:
<aurel...@aurel32.net>
Received:
from hall.aurel32.net ([88.191.82.174]) by busoni.debian.org with esmtps
(TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from
<aurel...@aurel32.net>) id 1OIfCJ-0006fX-4t for
583577-d...@bugs.debian.org; Sun, 30 May 2010 09:52:49 +0000
Received:
from aurel32 by hall.aurel32.net with local (Exim 4.69) (envelope-from
<aurel...@aurel32.net>) id 1OIfCF-0006ur-B6 for
583577-d...@bugs.debian.org; Sun, 30 May 2010 11:52:43 +0200
Message-ID:
<20100530095243.gf17...@hall.aurel32.net>
References:
<20100528123543.12614.67342.report...@se-booking2.emediate.eu>
MIME-Version:
1.0
Content-Type:
text/plain; charset=iso-8859-15
Content-Disposition:
inline
In-Reply-To:
<20100528123543.12614.67342.report...@se-booking2.emediate.eu>
X-Mailer:
Mutt 1.5.18 (2008-05-17)
User-Agent:
Mutt/1.5.18 (2008-05-17)
Sender:
Aurelien Jarno <aurel...@aurel32.net>
Version: 2.9-1
On Fri, May 28, 2010 at 02:35:43PM +0200, Erland Lewin wrote:
Package: libc6
Version: 2.7-18lenny2
Severity: important
The bug described in the glibc bug report at:
http://sourceware.org/bugzilla/show_bug.cgi?id=6419
seems to be present in Debian Lenny. Running the example program in the above
bug report causes a segmentation fault in pthread_mutex_timedlock, at least
on this hardware.
I think this is important because it is a bug in a core function.
This bug only affects Lenny, and has been fixed in version 2.9-1.
Marking it in the BTS.
------------------------------------------------------------------------
Subject:
libc6: pthread_mutex_timedlock can segfault
From:
Erland Lewin <erl...@emediate.se>
Date:
Fri, 28 May 2010 14:35:43 +0200
To:
Debian Bug Tracking System <sub...@bugs.debian.org>
To:
Debian Bug Tracking System <sub...@bugs.debian.org>
Received:
(at submit) by bugs.debian.org; 28 May 2010 12:36:09 +0000
X-Spam-Checker-Version:
SpamAssassin 3.2.5-bugs.debian.org_2005_01_02 (2008-06-10) on
busoni.debian.org
X-Spam-Bayes:
score:0.0000 Tokens: new, 30; hammy, 143; neutral, 37; spammy, 1.
spammytokens:0.968-+--H*r:bugs.debian.org
hammytokens:0.000-+--H*M:reportbug, 0.000-+--H*MI:reportbug,
0.000-+--H*x:reportbug, 0.000-+--H*UA:reportbug, 0.000-+--H*x:3.48
X-Spam-Status:
No, score=-12.3 required=4.0 tests=BAYES_00,FOURLA,HAS_PACKAGE,
RDNS_DYNAMIC,URIBL_CNKR,XMAILER_REPORTBUG,X_DEBBUGS_CC autolearn=ham
version=3.2.5-bugs.debian.org_2005_01_02
Return-path:
<erl...@emediate.se>
Received:
from 195-12-228-163.customer.teliacarrier.com ([195.12.228.163]
helo=se-booking2.emediate.eu) by busoni.debian.org with esmtp (Exim
4.69) (envelope-from <erl...@emediate.se>) id 1OHyn5-000206-WB for
sub...@bugs.debian.org; Fri, 28 May 2010 12:36:09 +0000
Content-Type:
text/plain; charset="us-ascii"
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
Message-ID:
<20100528123543.12614.67342.report...@se-booking2.emediate.eu>
X-Mailer:
reportbug 3.48
X-Debbugs-Cc:
erl...@emediate.se
Delivered-To:
sub...@bugs.debian.org
Package: libc6
Version: 2.7-18lenny2
Severity: important
The bug described in the glibc bug report at:
http://sourceware.org/bugzilla/show_bug.cgi?id=6419
seems to be present in Debian Lenny. Running the example program in the above
bug report causes a segmentation fault in pthread_mutex_timedlock, at least
on this hardware.
I think this is important because it is a bug in a core function.
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libc6 depends on:
ii libgcc1 1:4.3.2-1.1 GCC support library
libc6 recommends no packages.
Versions of packages libc6 suggests:
pn glibc-doc <none> (no description available)
ii locales 2.7-18lenny2 GNU C Library: National Language (
ii locales-all [locales] 2.7-18lenny2 GNU C Library: Precompiled locale
-- debconf information:
glibc/upgrade: true
glibc/restart-failed:
glibc/restart-services:
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
