Bug#203434: libc6: accessing thread-local storage causes SIGSEGV

To: Denis Barbier <barbier@linuxfr.org>
Cc: 203434@bugs.debian.org
Subject: Bug#203434: libc6: accessing thread-local storage causes SIGSEGV
From: Ben Liblit <liblit@cs.wisc.edu>
Date: Mon, 07 Nov 2005 16:20:28 -0600
Message-id: <[🔎] 436FD32C.7070200@cs.wisc.edu>
Reply-to: Ben Liblit <liblit@cs.wisc.edu>, 203434@bugs.debian.org
In-reply-to: <[🔎] 20051107221726.GA11000@linuxfr.org>
References: <[🔎] 20051107221726.GA11000@linuxfr.org>

Denis Barbier wrote:

It looks like this bug has been fixed in libc6 2.3.5, can it be closed?

I have no objection to closing the bug on the optimistic assumption thatthe fix exists and works. However, I no longer have a current Debianbox, so I am unable to actually confirm the fix myself.

Reply to:

References:
- Bug#203434: libc6: accessing thread-local storage causes SIGSEGV
  - From: Denis Barbier <barbier@linuxfr.org>

Prev by Date: Bug#179837: marked as done (libc6 postinst calls tzconfig on every upgrade)
Next by Date: Processed: severity of 322011 is grave, merging 322011 328440
Previous by thread: Bug#203434: libc6: accessing thread-local storage causes SIGSEGV
Next by thread: Bug#187630: marked as done (libc6: localedef uses . in its input path)
Index(es):
- Date
- Thread