public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kari.jyrkinen at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/14195] New: strncasecmp causes segmentation fault when comparing empty strings
Date: Mon, 04 Jun 2012 09:50:00 -0000	[thread overview]
Message-ID: <bug-14195-131@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 14195
           Summary: strncasecmp causes segmentation fault when comparing
                    empty strings
           Product: glibc
           Version: 2.15
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: unassigned@sourceware.org
        ReportedBy: kari.jyrkinen@gmail.com
                CC: drepper.fsp@gmail.com
    Classification: Unclassified


Minimal example:

#include <string.h>

int main(int argc, const char *argv[]) {
  char *p = "";
  return strncasecmp(p, "", 1);
}

It seems the return value is corrupted as the compiled program crashes only
when it is referenced. Crashes only on 32 bit and certain processors, might bet
when SSE3 and SSE4 are in use, as this problem appeared in the newest glibc and
there seems to be changes for it done:

* Optimized strcasecmp and strncasecmp for SSSE3 and SSE4.2 on x86-32.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-06-04  9:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04  9:50 kari.jyrkinen at gmail dot com [this message]
2012-06-05 15:19 ` [Bug libc/14195] " ppluzhnikov at google dot com
2012-06-06 13:21 ` hjl.tools at gmail dot com
2012-06-07 11:08 ` kari.jyrkinen at gmail dot com
2012-08-09 15:20 ` liubov.dmitrieva at gmail dot com
2012-08-09 15:21 ` liubov.dmitrieva at gmail dot com
2012-08-15 19:11 ` aj at suse dot de

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=bug-14195-131@http.sourceware.org/bugzilla/ \
    --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).