public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "starfire01 at astrofrontiers dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/751] regcomp calls malloc with 0 byte request size when pattern begins with BOL anchor '^'
Date: Tue, 27 Sep 2005 01:55:00 -0000	[thread overview]
Message-ID: <20050927015517.5822.qmail@sourceware.org> (raw)
In-Reply-To: <20050218045523.751.starfire01@astrofrontiers.com>


------- Additional Comments From starfire01 at astrofrontiers dot com  2005-09-27 01:55 -------
Subject: Re:  regcomp calls malloc with 0 byte request size
	when pattern begins with BOL anchor '^'

It's been over seven months since the submission, so I have no comment
as to why it cannot be reproduced other than the fact that changes have
been made to avoid the problem.  Close the bug report if you see fit.  I
was just trying to chip in.

Bruce
(Starfire-1)


On Tue, 2005-09-27 at 01:01 +0000, drepper at redhat dot com wrote:
> ------- Additional Comments From drepper at redhat dot com  2005-09-27 01:01 -------
> regcomp does not return an error for the code you showed for me.  And your
> second comment is confusing.  So, what is the deal?  I see no error and am
> inclined to just close the bug.
> 



-- 


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

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


  parent reply	other threads:[~2005-09-27  1:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-18  4:55 [Bug regex/751] New: " starfire01 at astrofrontiers dot com
2005-02-18 21:09 ` [Bug regex/751] " starfire01 at astrofrontiers dot com
2005-09-27  1:02 ` drepper at redhat dot com
2005-09-27  1:55 ` starfire01 at astrofrontiers dot com [this message]
2005-09-27  6:53 ` 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=20050927015517.5822.qmail@sourceware.org \
    --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).