This patch is already included in the Debian libc6 package. It actually
may be the cause of the problem you reported.
This problem is already fixed in 2.11.1 or master. Have you also applied
the proper _second_ patch in that bug? C.f. my and H.J.Lu's comments and
mailing list posts.
On Wed, Jan 27, 2010 at 11:47:42AM +0100, Petr Baudis wrote:
This patch is already included in the Debian libc6 package. It actually
may be the cause of the problem you reported.
This problem is already fixed in 2.11.1 or master. Have you also applied
the proper _second_ patch in that bug?
Gentile Cliente, debian-glibc@lists.debian.org
Il vostro servizio BancoPostaonline e scaduto. Dovete rinnovarlo
subito altrimenti il vostro conto verra chiuso.
Se volete usare questo servizio in futuro, dovete procedere
subito.
Per continuare, Il modulo di aggiornamento e`allegato a questa
On Mon, 25 Jan 2010, Aurelien Jarno wrote:
On Mon, Jan 25, 2010 at 09:08:08AM -0500, root wrote:
Package: libc6
Version: 2.7-18
Severity: critical
Justification: breaks unrelated software
I'm running Debian Lenny with a stock 2.6.26-2 AMD64 kernel, and after upgrading any of
my systems to
Subject: libc6: reproducable segfault in printf / vfprintf
Package: libc6
Version: 2.10.2-2
Justification: breaks the whole system
Severity: critical
after found a segfault problem in libc6 i have tried to construct a
minimal programm, that produce that error.
the following code produces this
Your message dated Wed, 27 Jan 2010 14:38:15 +0100
with message-id 20100127133815.ga21...@hall.aurel32.net
and subject line Re: Bug#567116: reproducable segfault in printf / vfprintf
has caused the Debian Bug report #567116,
regarding reproducable segfault in printf / vfprintf
to be marked as
Of cours,
you're right - compiling without -Wall -W was a mistake on reducing the
real code to that minimal example. But correcting the sample code in the
following way, so the argument order is correct doesn't help :
getopt/getopt_long is actually not supposed to return ':' if the
optstring does not _begin_ with a colon (e.g. :g:) or a +/- sign
followed by a colon (e.g. +:g - this actually has another bug, but
that's not what this report is about).
--
To UNSUBSCRIBE, email to
On Mon, Jan 25, 2010 at 04:03:38PM -0700, Dave Serls wrote:
On Mon, 25 Jan 2010 21:47:38 +0100
Aurelien Jarno aurel...@aurel32.net wrote:
On Mon, Jan 25, 2010 at 01:14:28PM -0700, Dave Serls wrote:
On Mon, 25 Jan 2010 21:06:49 +0100
Aurelien Jarno aurel...@aurel32.net wrote:
On
Processing commands for cont...@bugs.debian.org:
severity 538916 normal
Bug #538916 [libc6.1-dev] libc6.1-dev: Conflicting definitions in
linux/ptrace.h and sys/ptrace.h on ia64
Severity set to 'normal' from 'important'
thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
forwarded 563882 http://sourceware.org/bugzilla/show_bug.cgi?id=11230
Bug #563882 [libc6.1] ia64: memchr overshots
Set Bug forwarded-to-address to
'http://sourceware.org/bugzilla/show_bug.cgi?id=11230'.
thanks
Stopping processing here.
Please
forwarded 563882 http://sourceware.org/bugzilla/show_bug.cgi?id=11230
thanks
Hi Aurelian,
Aurelien Jarno wrote:
On Tue, Jan 26, 2010 at 04:06:32PM -0600, Jonathan Nieder wrote:
FYI: http://sourceware.org/bugzilla/show_bug.cgi?id=10162
Maybe glibc 2.11.1 (which includes a cherry-pick of
On Wed, Jan 27, 2010 at 12:33:26PM +0100, Aurelien Jarno wrote:
On Wed, Jan 27, 2010 at 11:47:42AM +0100, Petr Baudis wrote:
This patch is already included in the Debian libc6 package. It actually
may be the cause of the problem you reported.
This problem is already fixed in 2.11.1 or
13 matches
Mail list logo
