Parse error in checks, ¿why?

I’m checking my code but it says:
Checking Neuman.c …

[splint] splint................................................................Failed
hookid: splint

Neuman.c: (in function main)
Neuman.c:12:14: Possibly null storage fp passed as non-null param:
                   fscanf (fp, ...)
  A possibly null pointer is passed as a parameter corresponding to a formal
  parameter with no /*@null@*/ annotation.  If NULL may be used for this
  parameter, add a /*@null@*/ annotation to the function parameter declaration.
  (Use -nullpass to inhibit warning)
   Neuman.c:11:6: Storage fp may become null
Splint 3.1.2 --- 01 Dec 2016

Neuman.c:13:9: Parse Error. (For help on parse errors, see splint -help
             parseerrors.)
*** Cannot continue.

[rubocop] rubocop..........................................(no files to check)Skipped
[slim-lint] slim-lint......................................(no files to check)Skipped
Precommit failed
See (future:webpage docs|now:https://pre-commit.com/)
mimetypes and charsets check OK, continue checks...

can you explain me the problem, what means splint error

Searching in google for: null storage fp passed as non-null param + splint

Take me to: https://stackoverflow.com/questions/25179289/splint-and-mysql-null-storage-passed-as-non-null-param

Splint is the linter that checks for better programming practices.

1 Like

But, it wasn’t the error, it throw the same message

Checking Neuman.c ...

[splint] splint................................................................Failed
hookid: splint

Splint 3.1.2 --- 01 Dec 2016

Neuman.c:15:9: Parse Error. (For help on parse errors, see splint -help
               parseerrors.)
*** Cannot continue.

The point is that the Split linter failed, and it fails because find something that should be fixed in your solution. Try to run Splint locally and read and learn the type of errors that this kind of tool report on your code. We only admit fully-linted solutions in strictest mode, and the CI enforces this.

@previous-bell If this topic is solved, please mark it as such by checking the solution chart at the bottom of the post you consider that properly answers your question