CVSROOT: /webcvs/grep Module name: grep Changes by: Jim Meyering <meyering> 23/03/22 22:55:22
Index: html_node/Known-Bugs.html =================================================================== RCS file: /webcvs/grep/grep/manual/html_node/Known-Bugs.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -b -r1.4 -r1.5 --- html_node/Known-Bugs.html 3 Sep 2022 19:33:14 -0000 1.4 +++ html_node/Known-Bugs.html 23 Mar 2023 02:55:21 -0000 1.5 @@ -1,11 +1,11 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd";> +<!DOCTYPE html> <html> -<!-- Created by GNU Texinfo 6.8, https://www.gnu.org/software/texinfo/ --> +<!-- Created by GNU Texinfo 7.0dev, https://www.gnu.org/software/texinfo/ --> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <!-- This manual is for grep, a pattern matching engine. -Copyright (C) 1999-2002, 2005, 2008-2022 Free Software Foundation, +Copyright © 1999-2002, 2005, 2008-2023 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document @@ -14,10 +14,10 @@ Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". --> -<title>Known Bugs (GNU Grep 3.8)</title> +<title>Known Bugs (GNU Grep 3.10)</title> -<meta name="description" content="Known Bugs (GNU Grep 3.8)"> -<meta name="keywords" content="Known Bugs (GNU Grep 3.8)"> +<meta name="description" content="Known Bugs (GNU Grep 3.10)"> +<meta name="keywords" content="Known Bugs (GNU Grep 3.10)"> <meta name="resource-type" content="document"> <meta name="distribution" content="global"> <meta name="Generator" content="makeinfo"> @@ -29,21 +29,8 @@ <link href="Reporting-Bugs.html" rel="up" title="Reporting Bugs"> <style type="text/css"> <!-- -a.copiable-anchor {visibility: hidden; text-decoration: none; line-height: 0em} -a.summary-letter {text-decoration: none} -blockquote.indentedblock {margin-right: 0em} -div.display {margin-left: 3.2em} -div.example {margin-left: 3.2em} -kbd {font-style: oblique} -pre.display {font-family: inherit} -pre.format {font-family: inherit} -pre.menu-comment {font-family: serif} -pre.menu-preformatted {font-family: serif} -span.nolinebreak {white-space: nowrap} -span.roman {font-family: initial; font-weight: normal} -span.sansserif {font-family: sans-serif; font-weight: normal} -span:hover a.copiable-anchor {visibility: visible} -ul.no-bullet {list-style: none} +a.copiable-link {visibility: hidden; text-decoration: none; line-height: 0em} +span:hover a.copiable-link {visibility: visible} --> </style> <link rel="stylesheet" type="text/css" href="https://www.gnu.org/software/gnulib/manual.css";> @@ -52,20 +39,20 @@ </head> <body lang="en"> -<div class="section" id="Known-Bugs"> -<div class="header"> +<div class="section-level-extent" id="Known-Bugs"> +<div class="nav-panel"> <p> Up: <a href="Reporting-Bugs.html" accesskey="u" rel="up">Reporting bugs</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Index.html" title="Index" rel="index">Index</a>]</p> </div> <hr> -<span id="Known-Bugs-1"></span><h3 class="section">6.1 Known Bugs</h3> -<span id="index-Bugs_002c-known"></span> +<h3 class="section" id="Known-Bugs-1"><span>6.1 Known Bugs<a class="copiable-link" href="#Known-Bugs-1"> ¶</a></span></h3> +<a class="index-entry-id" id="index-Bugs_002c-known"></a> -<p>Large repetition counts in the ‘<samp>{n,m}</samp>’ construct may cause -<code>grep</code> to use lots of memory. +<p>Large repetition counts in the ‘<samp class="samp">{n,m}</samp>’ construct may cause +<code class="command">grep</code> to use lots of memory. In addition, certain other obscure regular expressions require exponential time and -space, and may cause <code>grep</code> to run out of memory. +space, and may cause <code class="command">grep</code> to run out of memory. </p> <p>Back-references can greatly slow down matching, as they can generate exponentially many matching possibilities that can consume both time @@ -74,13 +61,13 @@ expression implementations have back-reference bugs that can cause programs to return incorrect answers or even crash, and fixing these bugs has often been low-priority: for example, as of 2021 the -<a href="https://sourceware.org/bugzilla/";>GNU C library bug database</a> +<a class="url" href="https://sourceware.org/bugzilla/";>GNU C library bug database</a> contained back-reference bugs -<a href="https://sourceware.org/bugzilla/show_bug.cgi?id=52";>52</a>, -<a href="https://sourceware.org/bugzilla/show_bug.cgi?id=10844";>10844</a>, -<a href="https://sourceware.org/bugzilla/show_bug.cgi?id=11053";>11053</a>, -<a href="https://sourceware.org/bugzilla/show_bug.cgi?id=24269";>24269</a> -and <a href="https://sourceware.org/bugzilla/show_bug.cgi?id=25322";>25322</a>, +<a class="url" href="https://sourceware.org/bugzilla/show_bug.cgi?id=52";>52</a>, +<a class="url" href="https://sourceware.org/bugzilla/show_bug.cgi?id=10844";>10844</a>, +<a class="url" href="https://sourceware.org/bugzilla/show_bug.cgi?id=11053";>11053</a>, +<a class="url" href="https://sourceware.org/bugzilla/show_bug.cgi?id=24269";>24269</a> +and <a class="url" href="https://sourceware.org/bugzilla/show_bug.cgi?id=25322";>25322</a>, with little sign of forthcoming fixes. Luckily, back-references are rarely useful and it should be little trouble to avoid them in practical applications.
