Bug#614892: libc6: please apply upstream qsort() crash fix
Package: libc6 Version: 2.11.2-10 I noticed that msgmerge was randomly and intermittently dying with SIGFPE on multiple systems of mine. When I examined the core file, I saw that it was dying in qsort_r(). Some detective work showed that this was the following bug fixed in upstream glibc: http://sourceware.org/bugzilla/show_bug.cgi?id=11655 with the following commit: http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=fb88ac72c2dcbbd979c8798e4ea497818bb3e171 Since it makes some threaded programs crash randomly, it'd be nice to get this fixed. Thanks, Ben. -- Ben Pfaff http://benpfaff.org -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87k4gqjl3n@blp.benpfaff.org
Bug#177940: mktime.c fix
Otavio Salvador <[EMAIL PROTECTED]> writes: > || On Fri, 22 Oct 2004 12:54:34 +0900 > || GOTO Masanori <[EMAIL PROTECTED]> wrote: > > gm> Hi, > gm> At 30 Dec 2003 23:49:22 -0800, > gm> Paul Eggert wrote: >>> Jeff Bailey <[EMAIL PROTECTED]> writes: >>> >>> > It's been a while since I've looked at this, but it appears that the >>> > files should be identical, right? (All the #ifdef _LIBC constructs are >>> > still in place). If yes, I can put together a series of patches to get >>> > it back in sync. >>> >>> Thanks for volunteering! But I really should do it, since I wrote >>> mktime.c and understand the patches well. >>> >>> I'll send the proposed patches to libc-alpha, since Ulrich won't let >>> me send email to libc-hacker. If nothing happens for a while, I >>> suppose that you can copy the patches to libc-hacker. > > gm> Is this patch still needed? > > I'm not sure. I didn't test it since the report. I reran the test that I did for the original bug report and still see the error even with the latest `unstable' libc6 in Debian (2.3.2.ds1-18). In fact it appears to be worse because now it reports that mktime doesn't work for every timezone I tried (America/Sao_Paulo, US/Pacific, GMT), e.g.: [EMAIL PROTECTED]:~/tmp$ TZ=GMT ./configure checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking whether time.h and sys/time.h may both be included... yes checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for stdlib.h... (cached) yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking for unistd.h... (cached) yes checking for alarm... yes checking for working mktime... no configure: creating ./config.status -- Ben Pfaff email: [EMAIL PROTECTED] web: http://benpfaff.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#243885: Bug#240887: Package building problem.
Herbert Xu <[EMAIL PROTECTED]> writes: >> Accordingly, I believe that the pattern in your example means >> "backslash, followed by a, followed by closing square bracket", not what >> you think it means. > > You're quite right. This is reaffirmed by the POSIX document for > basic regular expressions, which is what POSIX uses to define > shell patterns. > > Therefore tetex-bin and autoconf will need to be fixed instead to > not use backslashes in [] expressions. I read through the entire bug log for 240887 and couldn't figure out what actual bug in Autoconf is being pointed out. Can anyone help me out? I can't fix a bug if no one tells me what the bug is. -- "Mon peu de succÃs prÃs des femmes est toujours venu de les trop aimer." --Jean-Jacques Rousseau
Bug#243885: Bug#240887: Package building problem.
Herbert Xu <[EMAIL PROTECTED]> writes: >> Accordingly, I believe that the pattern in your example means >> "backslash, followed by a, followed by closing square bracket", not what >> you think it means. > > You're quite right. This is reaffirmed by the POSIX document for > basic regular expressions, which is what POSIX uses to define > shell patterns. > > Therefore tetex-bin and autoconf will need to be fixed instead to > not use backslashes in [] expressions. I read through the entire bug log for 240887 and couldn't figure out what actual bug in Autoconf is being pointed out. Can anyone help me out? I can't fix a bug if no one tells me what the bug is. -- "Mon peu de succÃs prÃs des femmes est toujours venu de les trop aimer." --Jean-Jacques Rousseau
Bug#46547: glibc-doc: typo
Package: glibc-doc Version: 2.1.2-5 Node "Basic CPU Time" in the documentation says the following: measured by the `clock' function. POSIX requires that this value is one million independend of the actual resolution. ^^^ misspelled (should end in `t') -- "Whoever you are -- SGI, SCO, HP, or even Microsoft -- most of the smart people on the planet work somewhere else." --Eric S. Raymond