Hello,
I have a problem that the newest cppcheck crashes when checking one file. Is there any other possibility to see what cppcheck is doing than --verbose?
I need to switch some other logging on.
Thank you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you can reduce the code triggering the crash to a small example it would be good to report on http://trac.cppcheck.net/ - burdening the developers with the analysis.
Switches about verbose or debug output are IMHO unlikely to help in analysis.
I don't know which operating system and which binary you are currently using. If you are using the GUI version the only chance is running the executable in the debugger. In case of the command line version you might try the --exception-handling switch and then consider reporting a bug as outlined above.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry, I am not able to add the ticket to your trac system - I was not successful with creating account there. Could you please create one for me? I use windows.
The problem:
20:13:56 Checking \source\MFCPLUS.CPP...
20:13:56 Internal error: Access violation reading from 0x24
20:13:56 0. 0x68FF22C7 in CheckVaarg::va_start_argument
20:13:56 1. 0x002BF514 in CheckVaarg::va_start_argument
20:13:56 2. 0x769814AD in HeapFree
20:13:56 3. 0x68FF4572 in CppCheck::checkFile
20:13:56 Please report this to the cppcheck developers!
Just info - previous version 1.50 did not have the problem with the file.
Last edit: kerinek 2015-02-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I have a problem that the newest cppcheck crashes when checking one file. Is there any other possibility to see what cppcheck is doing than --verbose?
I need to switch some other logging on.
Thank you.
If you can reduce the code triggering the crash to a small example it would be good to report on http://trac.cppcheck.net/ - burdening the developers with the analysis.
Switches about verbose or debug output are IMHO unlikely to help in analysis.
I don't know which operating system and which binary you are currently using. If you are using the GUI version the only chance is running the executable in the debugger. In case of the command line version you might try the --exception-handling switch and then consider reporting a bug as outlined above.
Sorry, I am not able to add the ticket to your trac system - I was not successful with creating account there. Could you please create one for me? I use windows.
The problem:
20:13:56 Checking \source\MFCPLUS.CPP...
20:13:56 Internal error: Access violation reading from 0x24
20:13:56 0. 0x68FF22C7 in CheckVaarg::va_start_argument
20:13:56 1. 0x002BF514 in CheckVaarg::va_start_argument
20:13:56 2. 0x769814AD in HeapFree
20:13:56 3. 0x68FF4572 in CppCheck::checkFile
20:13:56 Please report this to the cppcheck developers!
Just info - previous version 1.50 did not have the problem with the file.
Last edit: kerinek 2015-02-21
As for the account: can you pls read https://sourceforge.net/p/cppcheck/discussion/development/thread/e506a73d/ for additional info?
Regarding the code:
If you have a small example you might share it e.g. on http://codepad.org/
BTW which version do you use?