Bug#586241: libc6: Upgrade 2.10.2-9 to 2.11.1-3 breaks the system debian/squeeze, (segfaults on any command)

Hello, Here it is: http://dl.free.fr/rr9lPsFSJ It should be faster than if I hosted it myself. Some sha1sum: 3157273da1dcd2b7681e918599219105a7ede22d pluton.libc6.sda 8fc949f3596376f0885043b8f820664308857f79 pluton.libc6.sda.lzma It contains the whole crashed filesystem (you can check the /

Bug#586971: libc6-dev: REG_NOSUB prevents storing location of entire regex match

Package: libc6-dev Version: 2.11.1-3 Severity: minor Tags: upstream /usr/include/regex.h says: /* If this bit is set, then report only success or fail in regexec. If not set, then returns differ between not matching and errors. */ #define REG_NOSUB (REG_NEWLINE << 1) It doesn't say anything

Bug#586241: libc6: Upgrade 2.10.2-9 to 2.11.1-3 breaks the system debian/squeeze, (segfaults on any command)

On Tue, Jun 22, 2010 at 10:15:59PM +0200, Thibault Manlay wrote: > On 21/06/10 01:01, Aurelien Jarno wrote: >> >> If you are able again to produce an image with libc6 crashing (I mean >> already crashing, not that will crash after an upgrade), that's probably >> something we can already study. > >

Bug#586241: libc6: Upgrade 2.10.2-9 to 2.11.1-3 breaks the system debian/squeeze, (segfaults on any command)

Hello, On Tue, Jun 22, 2010 at 10:15:59PM +0200, Thibault Manlay wrote: > On 21/06/10 01:01, Aurelien Jarno wrote: >> If you are able again to produce an image with libc6 crashing (I mean >> already crashing, not that will crash after an upgrade), that's probably >> something we can already study.

Bug#586241: libc6: Upgrade 2.10.2-9 to 2.11.1-3 breaks the system

On Wed, Jun 23, 2010 at 10:18:28PM +0300, Alexander Gattin wrote: > had the same situation several days ago, libc > became corrupt (no process could be started, > including /sbin/init). here's excerpt from dpkg.log: 2010-06-20 02:14:41 upgrade libc6 2.10.2-9 2.11.1-3 2010-06-20 02:14:41 status ha

Bug#586241: libc6: Upgrade 2.10.2-9 to 2.11.1-3 breaks the system

Hello, had the same situation several days ago, libc became corrupt (no process could be started, including /sbin/init). I had no busybox-static on this system, only sash, but it wasn't very helpful -- no tar/gzip/lvm2 tools available from sash on this broken system anyway. I booted off a USB fl

Bug#586883: libc6: printf doesn't return a negative value in case of output error

forwarded 586883 http://sourceware.org/bugzilla/show_bug.cgi?id=11741 thanks -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, em

Processed: Re: libc6: printf doesn't return a negative value in case of output error

Processing commands for cont...@bugs.debian.org: > forwarded 586883 http://sourceware.org/bugzilla/show_bug.cgi?id=11741 Bug #586883 [libc6] libc6: printf doesn't return a negative value in case of output error Set Bug forwarded-to-address to 'http://sourceware.org/bugzilla/show_bug.cgi?id=11741

Bug#586883: libc6: printf doesn't return a negative value in case of output error

Package: libc6 Version: 2.11.2-1 Severity: normal For fprintf (thus printf), the C standard says: The fprintf function returns the number of characters transmitted, or a negative value if an output or encoding error occurred. But in glibc, printf doesn't return a negative value in case of ou