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

Re: Fwd: New Defects reported by Coverity Scan for git

From
Jeff King <peff@peff.net>
Date
Oct 20, 2016, 21:40 UTC
Message-ID
<20161020214045.gpe352xnw5oc36ur@sigill.intra.peff.net>
In-Reply-To
<CAGZ79kabVPhp0_z-e_4jJOFq+jzSE2SsgmFuY-2RUgrEviGKyA@mail.gmail.com>
On Thu, Oct 20, 2016 at 10:05:38AM -0700, Stefan Beller wrote:
> Not sure what triggered the new finding of coverity as seen below as the
> parse_commit() was not touched. Junios series regarding the merge base
> optimization touches a bit of code nearby though.

I have noticed that "old" problems sometimes reappear when nearby code changes. I assume that they have some kind of heuristic to identify the location of a defect, that it probably includes the line number in the file, and that it can be fooled by too much code appearing nearby.

-Peff
Previous: Junio C Hamano
Message 9 of 9 in “Fwd: New Defects reported by Coverity Scan for git”
  1. Stefan BellerOct 20, 2016
  2. Junio C HamanoOct 20, 2016
  3. Stefan BellerOct 20, 2016
  4. Junio C HamanoOct 20, 2016
  5. commit parsing: replace unchecked parse_commit by parse_commit_or_dieStefan Beller, Oct 20, 2016
  6. Stefan BellerOct 20, 2016
  7. Jeff KingOct 20, 2016
  8. Junio C HamanoOct 20, 2016
  9. Jeff KingOct 20, 2016

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.