cppcheclipse uses file names on command-line (instead of from file with --file-list) which limits the amount of files that can be used as input about cppcheclipse HOT 12 CLOSED

The null pointer exception from the error log is not really the cause, but 
rather a follow up error (it appears because the console cannot be opened 
correctly). That issue is already tracked in issue 54. Please provide me with 
the full console and error log as the real cause should have been logged before 
the null pointer exception.

How do I get full console and error log? The real cause is the too long 
command-line input.

After selecting a directory in the eclipse navigator, then this should be 
passed to the executable.

The help information, when using cppcheck from a command line, states:

-->
If a directory is given instead of a filename, *.cpp, *.cxx, *.cc, *.c++, *.c,
*.tpp, and *.txx files are checked recursively from the given directory.
<--

However, when starting the executable from within Eclipse selecting a folder 
containing >3400 files lists each file individually and issues the error:

-->
CreateProcess error=206, The filename or extension is too long) Maybe more 
information is available in the console view.
<--

[deleted comment]

[deleted comment]

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=327193 and 
http://msdn.microsoft.com/en-us/library/windows/desktop/ms682425%28v=vs.85%29.as
px for the relevant limits on Windows. It seems to be 32,768 characters.

For Unix systems have a look at that table: 
http://www.in-ulm.de/~mascheck/various/argmax/.
The workarounds could be:
a) pass complete directories instead of single filenames to cppcheck
b) use a separate file to give the filenames to check

a) has the drawback of also imposing a limit (in case there are a lot of 
directories or only some files are relevant within one directory)
b) has the drawback that another file needs to be created before cppcheck is 
launched (and afterwards deleted).

According to the help file of cppcheck 1.62 the list of files to be checked can 
also be provided on the stdin.

This issue was closed by revision r298.

This issue was closed by revision r301.

Update: This is already supported with Cppcheck in version 1.56.