public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/1281] New: support 64-bit hosts when regex code when used outside glibc
Date: Wed, 31 Aug 2005 22:43:00 -0000	[thread overview]
Message-ID: <20050831224259.1281.eggert@gnu.org> (raw)

On 64-bit hosts (where size_t is 64 bits and int is 32 bits), the
old glibc regex code mishandles strings longer than 2**31 bytes.
The attached patch fixes this when the regex code is used in gnulib
(i.e., outside glibc).

This patch should not affect the use of the regex code inside
glibc.  No doubt this problem also needs to be handled for glibc
as well, but the result will be an incompatible change to the
glibc ABI, and the old ABI will have to be supported too.  That
can be the the subject for another patch.

-- 
           Summary: support 64-bit hosts when regex code when used outside
                    glibc
           Product: glibc
           Version: 2.3.5
            Status: NEW
          Severity: normal
          Priority: P2
         Component: regex
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: eggert at gnu dot org
                CC: glibc-bugs-regex at sources dot redhat dot com,glibc-
                    bugs at sources dot redhat dot com
 BugsThisDependsOn: 1220


http://sources.redhat.com/bugzilla/show_bug.cgi?id=1281

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


             reply	other threads:[~2005-08-31 22:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-31 22:43 eggert at gnu dot org [this message]
2005-08-31 22:43 ` [Bug regex/1281] " eggert at gnu dot org
2005-08-31 23:34 ` eggert at gnu dot org
2005-09-01  6:59 ` eggert at gnu dot org
2005-09-01  7:05 ` bonzini at gnu dot org
2005-09-01 18:32 ` eggert at gnu dot org
2005-09-01 22:09 ` eggert at gnu dot org
2005-09-01 22:19 ` eggert at gnu dot org
2005-09-01 22:20 ` eggert at gnu dot org
2005-09-06 18:11 ` drepper at redhat dot com
2005-09-06 23:47 ` drepper at redhat dot com
2006-04-19 17:43 ` bruno at clisp dot org
2006-04-25 18:01 ` drepper at redhat dot com
2006-04-25 18:20 ` drepper at redhat dot com
2006-04-25 22:54 ` drepper at redhat 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=20050831224259.1281.eggert@gnu.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs-regex@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).