[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#13978: marked as done (libc6: cannot run mysqld with libpthreads in 2.0.5; patch)

Your message dated Tue, 11 May 1999 07:15:52 -0700
with message-id <v04204e02b35dbedd995a@[]>
and subject line Fixed or no longer applicable.
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'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Ian Jackson
(administrator, Debian bugs database)

Received: (at submit) by bugs.debian.org; 18 Oct 1997 16:57:22 +0000
Received: (qmail 18955 invoked from network); 18 Oct 1997 16:57:21 -0000
Received: from (HELO kirby.shcon.com) (mail@
  by with SMTP; 18 Oct 1997 16:57:21 -0000
Received: from shanson by kirby.shcon.com with local (Exim 1.71 #1)
	id 0xMcGD-0001hN-00 (Debian); Sat, 18 Oct 1997 19:01:57 +0200
From: Scott Hanson <shanson@shcon.com>
Subject: libc6: cannot run mysqld with libpthreads in 2.0.5; patch
To: submit@bugs.debian.org
X-Mailer: bug 2.95
Message-Id: <E0xMcGD-0001hN-00@kirby.shcon.com>
Date: Sat, 18 Oct 1997 19:01:57 +0200

Package: libc6
Version: 2.0.5c-0.1

I'm trying to become the new maintainer of the mysql package, but
neither I nor Christian Schwarz (the previous maintainer) are able to
build a package where mysqld doesn't seg fault under libc6-2.0.5. However, replacing the libpthreads library with that from 2.0.4 seems to fix the problem.

On the mailing list for mysql, the following short patch for libc6 was included. I tried it, and it seems to solve the problem with mysqld, but of course I have no idea what other problems it may cause.

We'll probably have to release libc5 versions of mysql until this problem is fixed.


The following was posted by mf@fishbone.ruhr.de (Martin Fischer) on
the mysql mailing list:
> There is a bug in glibc-2.0.5, you can check the mail archive how to
> fix this. It's supposedly to be fixed in glibc 2.0.6.

I've the same environment and made a patch for the linuxthreads from

diff -uNr specific.c.orig specific.c
--- specific.c.orig	Tue Aug  5 16:17:39 1997
+++ specific.c	Wed Oct 15 21:45:00 1997
@@ -100,8 +100,6 @@
   unsigned int round;
   pthread_descr self = thread_self();
-  for (round = 0; round < PTHREAD_DESTRUCTOR_ITERATIONS; ++round)
-    {
       int found_nonzero = 0;
       unsigned int i;
       destr_function destr;
@@ -117,9 +115,5 @@
 	      found_nonzero |= self->p_specific[i] != NULL;
-      if (found_nonzero == 0)
 	/* No more non-NULL data with destructor.  */
-	break;
-    }

I've compiled mysql-3.20.29 without any problems and it runs fine
now. Ulrich Drepper, the developer of glibc, has written me, that
it is okay to delete the above lines in the linuxthreads-library
because it's an doubtful feature of POSIX.1c used rarely. The worst
case is that programs don't give back their memory immediately ; this
happens then at the programs end. An official patch for linuxthreads
will be in glibc-2.1, available in some weeks.

-- System Information
Debian Release: 1.3
Kernel Version: Linux kirby 2.0.31 #1 Sun Oct 5 14:02:39 CEST 1997 i586 unknown

Versions of the packages libc6 depends on:
ldso	Version: 1.9.6-2

Reply to: