public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug regex/1101] avoid dynamically sized stack arrays in regex Date: Mon, 18 Jul 2005 03:16:00 -0000 [thread overview] Message-ID: <20050718031654.28879.qmail@sourceware.org> (raw) In-Reply-To: <20050718031520.1101.roland@gnu.org> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-07-18 03:16 ------- Subject: Bug 1101 CVSROOT: /cvs/glibc Module name: libc Branch: glibc-2_3-branch Changes by: roland@sources.redhat.com 2005-07-18 03:16:51 Modified files: posix : regex_internal.c Log message: 2005-07-05 Ulrich Drepper <drepper@redhat.com> [BZ #1101] * posix/regex_internal.c (build_wcs_buffer): Use MB_LEN_MAX not MB_CUR_MAX. (build_wcs_upper_buffer): Likewise. 2005-03-05 Ulrich Drepper <drepper@redhat.com> [BZ #1101] * posix/regex_internal.c [_LIBC] (build_wcs_buffer): Avoid using dynamically sized array. (build_wcs_upper_buffer): Likewise. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/posix/regex_internal.c.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=1.45&r2=1.45.2.1 -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=1101 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-07-18 3:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-18 3:15 [Bug regex/1101] New: " roland at gnu dot org 2005-07-18 3:16 ` cvs-commit at gcc dot gnu dot org [this message] 2005-07-19 3:31 ` [Bug regex/1101] " roland at gnu dot org
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=20050718031654.28879.qmail@sourceware.org \ --to=sourceware-bugzilla@sources.redhat.com \ --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: linkBe 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).