Bug#481543: marked as done (libc6: low-memory snprintf provokes internal segfault)
Your message dated Sun, 12 Oct 2008 22:37:56 +0200
with message-id <20081012203756.GA17790@volta.aurel32.net>
and subject line Re: Bug#481543: libc6: low-memory snprintf provokes internal segfault
has caused the Debian Bug report #481543,
regarding libc6: low-memory snprintf provokes internal segfault
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
481543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481543
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libc6: low-memory snprintf provokes internal segfault
- From: Jim Meyering <meyering@rho.meyering.net>
- Date: Fri, 16 May 2008 22:30:34 +0200
- Message-id: <87hccy56w9.fsf@rho.meyering.net>
Package: libc6
Version: 2.7-11
Severity: normal
glibc's snprintf function malfunctions (segfault)
when its internal memory allocation fails.
FYI, this bug is new in libc6 2.7-11. I noticed because it provokes
a new failure in coreutils' printf-surprise test. This is not a
problem when using rawhide's glibc-2.8.
$ cat snprintf-test-debbug.c
#include <stdio.h>
#include <string.h>
int
main(int argc, char **argv)
{
char buf[200];
char *fmt = argv[1];
if (argc < 2)
return 1;
return snprintf (buf, sizeof buf, fmt, 1);
}
$ gcc snprintf-test-debbug.c
$ zsh -c 'ulimit -v 5000; ./a.out %$[5*2**20]d'
zsh: segmentation fault zsh -c 'ulimit -v 5000; ./a.out %$[5*2**20]d'
[Exit 139 (SEGV)]
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-1-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages libc6 depends on:
ii libgcc1 1:4.3.0-4 GCC support library
libc6 recommends no packages.
-- debconf information:
glibc/upgrade: true
glibc/restart-failed:
glibc/restart-services:
--- End Message ---
--- Begin Message ---
- To: 481543-done@bugs.debian.org
- Subject: Re: Bug#481543: libc6: low-memory snprintf provokes internal segfault
- From: Aurelien Jarno <aurelien@aurel32.net>
- Date: Sun, 12 Oct 2008 22:37:56 +0200
- Message-id: <20081012203756.GA17790@volta.aurel32.net>
- In-reply-to: <4885DA6B.20105@aurel32.net>
- References: <87hccy56w9.fsf@rho.meyering.net> <20080602160231.GC18631@hall.aurel32.net> <4885DA6B.20105@aurel32.net>
On Tue, Jul 22, 2008 at 03:02:35PM +0200, Aurelien Jarno wrote:
> Aurelien Jarno a écrit :
> > tag 481543 + unreproducible
> > tag 481543 + moreinfo
> > thanks
> >
> > On Fri, May 16, 2008 at 10:30:34PM +0200, Jim Meyering wrote:
> >> Package: libc6
> >> Version: 2.7-11
> >> Severity: normal
> >>
> >> glibc's snprintf function malfunctions (segfault)
> >> when its internal memory allocation fails.
> >> FYI, this bug is new in libc6 2.7-11. I noticed because it provokes
> >> a new failure in coreutils' printf-surprise test. This is not a
> >> problem when using rawhide's glibc-2.8.
> >>
> >>
> >> $ cat snprintf-test-debbug.c
> >> #include <stdio.h>
> >> #include <string.h>
> >> int
> >> main(int argc, char **argv)
> >> {
> >> char buf[200];
> >> char *fmt = argv[1];
> >> if (argc < 2)
> >> return 1;
> >> return snprintf (buf, sizeof buf, fmt, 1);
> >> }
> >> $ gcc snprintf-test-debbug.c
> >> $ zsh -c 'ulimit -v 5000; ./a.out %$[5*2**20]d'
> >> zsh: segmentation fault zsh -c 'ulimit -v 5000; ./a.out %$[5*2**20]d'
> >> [Exit 139 (SEGV)]
> >
> > I am unable to reproduce this problem. Moreover version 2.7-11 doesn't
> > introduce any change in this area.
> >
> > Please check that the bug is still reproducible on your system and that
> > downgrading to 2.7-10 actually fixes the problem.
> >
>
> Any news on that?
>
No answer from the submitter after a few pings. Closing the bugs.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
--- End Message ---
Reply to: