git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] grep: print the pcre2_jit_on value

From
Beat Bolli <dev+git@drbeat.li>
Date
Jul 22, 2019, 18:19 UTC
Message-ID
<20190722181923.21572-1-dev+git@drbeat.li>

When pcre2_jit_on is neither 1 nor 0, the BUG() call printed the value of pcre1_jit_on.

Print the value of pcre2_jit_on instead.
Signed-off-by: Beat Bolli <dev+git@drbeat.li>
---
 grep.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/grep.c b/grep.c
index f7c3a5803e..cd952ef5d3 100644
--- a/grep.c
+++ b/grep.c
@@ -559,7 +559,7 @@ static void compile_pcre2_pattern(struct grep_pat *p, const struct grep_opt *opt
 		pcre2_jit_stack_assign(p->pcre2_match_context, NULL, p->pcre2_jit_stack);
 	} else if (p->pcre2_jit_on != 0) {
 		BUG("The pcre2_jit_on variable should be 0 or 1, not %d",
-		    p->pcre1_jit_on);
+		    p->pcre2_jit_on);
 	}
 }
 
-- 
2.21.0.1020.gf2820cf01a
Next: Junio C Hamano
Message 1 of 6 in “grep: print the pcre2_jit_on value”
  1. grep: print the pcre2_jit_on valueBeat Bolli, Jul 22, 2019
  2. Junio C HamanoJul 23, 2019
  3. Johannes SchindelinJul 23, 2019
  4. Beat BolliJul 24, 2019
  5. Johannes SchindelinJul 25, 2019
  6. Carlo ArenasJul 29, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.