crash on using the cppcheck plu in

[frithjofh]

Hi everybody,

just received two times the same crash during execution of the cppcheck plugin on the c::b source itself. attached two crash reports. execution of cppcheck on my own project which is very much smaller does work fine and as expected. using c::b svn 5929 on suse 11.1 x64.

maybe it is a question of size?

would it be possible that plugins like this one would also obey the setting of the the "Build target" instead always work on the whole workspace?

regards

nausea

[attachment deleted by admin]

[Jenna]

The problem is the length of the commandline (32768 characters are allowed), but the C::B sources are too large.
The same happens for the cccc-plugin.

It should be possible to make the programs read the filenames from standard input stream.

I'm not sure how easy it is to do this, but using C::B's pipedprocess (or a pure wxProcess ?) might be the solution.

[killerbot]

yes, currently file names are handed over as command line parameters.
Therefor to big projects will give rise to to long command lines.
That's indeed something to improve.

[killerbot]

some information.

I have created a patch/improvement for CppCheck which got applied. It allows the files to be specified in a file, which is then passed on the command line.
This will be available in CppCheck 1.41, which will be released early march.
At that moment I will adopt the CppCheck plug-in.

The only thing I am in doubt of at this moment, is to keep supporting the current style, and have the plug-in use that old style when the version is older then 1.41, and when the version is 1.41 or above use the new style.

For the moment I am thinking of only doing the new style, and require people to have an up to date CppCheck.

[MortenMacFly]

For the moment I am thinking of only doing the new style, and require people to have an up to date CppCheck.

I would prefer that, too. As otherwise crash reports like below will be "normal".