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

Re: Errors and other unpleasant things found by Cppcheck

From
Philip Oakley <philipoakley@iee.org>
Date
Jan 8, 2018, 11:43 UTC
Message-ID
<5D41958DFAC74BD8B69761D171C572DB@PhilipOakley>
In-Reply-To
<5fb2c981-7a7b-5a0f-f2bb-b16189980d9b@arcor.de>
From: "Friedrich Spee von Langenfeld" <stehlampen@arcor.de>
Show 7 quoted lines
> Hi,
>
> I analyzed the GitHub repository with Cppcheck. The resulting XML file
> is attached. Please open it in Cppcheck to view it comfortably.
>
> Especially the bunch of errors could be of interest to you.
>
Hi,
Thanks for the submission.

The list prefers that useful information is in plain text so as to avoid opening file types that may hide undesirable effects.

Was your analysis part of an organised scan, or a personal insight? It would help to know the background.

The project does have a number of known and accepted cases of 'unitialised variables' and known memory leaks which are acceptable in those cases.

If you picked out the few key issues that you feel should be addressed then a patch can be considered, e.g. the suggestion of the wildmatch macro (L263) that depends on the order of evaluation of side effects.

-- Philip

Previous: Friedrich Spee von Langenfeld
Message 2 of 2 in “Errors and other unpleasant things found by Cppcheck”
  1. Friedrich Spee von LangenfeldJan 6, 2018
  2. Philip OakleyJan 8, 2018

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.