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

Re: segfault bug in internal git grep from next (fixed)

From
MRMarco Roeland <marco.roeland@xs4all.nl>
Date
May 4, 2006, 08:44 UTC
Message-ID
<20060504084418.GA10195@fiberbit.xs4all.nl>
In-Reply-To
<20060503083229.GA15579@fiberbit.xs4all.nl>
On Wednesday May 3rd 2006 Marco Roeland wrote:
> I'm using the next branch as of commit 6a40327d242dac9f85c6d63c94d537b45ba86e89
> 
> A segfault occurs in using the new builtin grep when using it on a
> binary file, so no regular \n endings.
Fixed by Junio in commit 7ed36f56e33bd838d06521a37a916516397e9e8b.

I really use git grep a lot. It is very powerful, and the builtin version makes even more possible. Thanks very much,

-- 
Marco Roeland
Previous: Marco Roeland
Message 2 of 2 in “segfault bug in internal git grep from next”
  1. Marco RoelandMay 3, 2006
  2. Marco RoelandMay 4, 2006

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.