From: Decklin Foster <fosterd@hartwick.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: matching bug
Date: Sat, 15 Apr 2000 23:49:45 -0400 [thread overview]
Message-ID: <20000415234945.A16383@photek.dhs.org> (raw)
I was reminded today that I planned to forward this here:
http://www.debian.org/Bugs/db/62/62339.html
This is a bug report which notes that rc segfaults if you attempt to
match '*' against the null list ("~ () '*'"). unquoted * is ok.
A quick trace shows that p->m is null (from what i can gather, this
means there are no metacharacters in p->w. documentation on the List
structure would be appreciated).
This is the line we crash on:
if (p->w[i] != '*' || p->m[i] != 1)
I'm a bit wary of just taking a check for non-NULL p->m on here, since
I don't understand what that means (other than the fact that with an
unquoted *, it's a pointer to "\001"). It seems like the function
really ought to be rewritten.
--
Written with 100% free software. Please support the following websites:
www.debian.org www.noamazon.com www.gnu.org www.opendvd.org lpf.ai.mit.edu
reply other threads:[~2000-04-17 20:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20000415234945.A16383@photek.dhs.org \
--to=fosterd@hartwick.edu \
--cc=rc@hawkwind.utcs.toronto.edu \
/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 NNTP newsgroup(s).