From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: re-search-forward/backward causes a segmentation fault
Date: Mon, 13 Oct 2003 14:21:33 -0400 [thread overview]
Message-ID: <E1A97K1-0008PQ-68@fencepost.gnu.org> (raw)
In-Reply-To: <200310130211.LAA22568@etlken.m17n.org> (message from Kenichi Handa on Mon, 13 Oct 2003 11:11:43 +0900 (JST))
I see. So, regex_compile should check the size of offset
before storing it in a buffer for compiled code. But,
doesn't it mean that if regex_compile does that check, we
don't have to have the limit of 2^16 as below?
regex_compile is the place that checks, and I am going to cut the
value of MAX_BUF_SIZE by 50%.
prev parent reply other threads:[~2003-10-13 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200310082328.IAA16073@etlken.m17n.org>
2003-10-11 5:37 ` re-search-forward/backward causes a segmentation fault Richard Stallman
2003-10-13 2:11 ` Kenichi Handa
2003-10-13 18:21 ` Richard Stallman [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1A97K1-0008PQ-68@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).