public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "jim at meyering dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/12348] re_match_2, re_search_internal, etc. infloop on persistent failing calloc
Date: Mon, 27 Dec 2010 07:53:00 -0000	[thread overview]
Message-ID: <bug-12348-132-MAMsFN6bV1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12348-132@http.sourceware.org/bugzilla/>

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

jim@meyering.net <jim at meyering dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #5167|0                           |1
        is obsolete|                            |

--- Comment #3 from jim at meyering dot net <jim at meyering dot net> 2010-12-27 07:53:10 UTC ---
Created attachment 5168
  --> http://sourceware.org/bugzilla/attachment.cgi?id=5168
do not cause search to infloop on calloc failure

heh. get both git log and ChangeLog entries right.

-- 
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.


  parent reply	other threads:[~2010-12-27  7:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27  7:36 [Bug regex/12348] New: " jim at meyering dot net
2010-12-27  7:37 ` [Bug regex/12348] " jim at meyering dot net
2010-12-27  7:44 ` jim at meyering dot net
2010-12-27  7:53 ` jim at meyering dot net [this message]
2010-12-27 16:37 ` jim at meyering dot net
2010-12-27 23:21 ` drepper.fsp at gmail dot com
2014-06-27 14:16 ` fweimer 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=bug-12348-132-MAMsFN6bV1@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --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).