public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "boringuy at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/5950] New: strtold_l() segfaults on various distribution of linux
Date: Mon, 17 Mar 2008 16:33:00 -0000	[thread overview]
Message-ID: <20080317163230.5950.boringuy@gmail.com> (raw)

I have tried glibc 2.5, 2.6 and 2.7 (none of them are available to select above
in the bug form). I have tried on Gentoo, Arch and Debian etch. I have tried on
64-bit and 32-bit machines. They all segfaults. Here is the test case:

#define _GNU_SOURCE 1
#include <xlocale.h>
#include <stdlib.h>

int main() {
    __locale_t x = NULL;
    strtold_l("1234.23423", NULL, x); 
    return 0;
}

Compile with this:
gcc -Wall -g -O2 -o test test.c

I have tried gcc3 and gcc4 and had the same result.

-- 
           Summary: strtold_l() segfaults on various distribution of linux
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: boringuy at gmail dot com
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=5950

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2008-03-17 16:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 16:33 boringuy at gmail dot com [this message]
2008-03-17 16:38 ` [Bug libc/5950] " rsa at us dot ibm dot com
2008-03-17 16:53 ` jakub at redhat dot com
2008-03-17 17:01 ` boringuy at gmail dot com
2008-03-17 17:11 ` jakub at redhat dot com
2008-03-17 17:29 ` rsa at us dot ibm dot com
2008-03-17 17:31 ` rsa at us dot ibm dot com
2008-03-17 17:59 ` rsa at us dot ibm dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080317163230.5950.boringuy@gmail.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).