The checking of the file will be interrupted because there are too many #ifdef configurations. Checking of all #ifdef configurations can be forced by --force command line option or from GUI preferences. However that may increase the checking time. (detailed CWE explanation)
The scope of the variable tmpx can be reduced. Warning: Be careful when fixing this message, especially when there are inner loops. Here is an example where cppcheck will write that the scope for i can be reduced:\012void f(int x)\012{\012 int i = 0;\012 if (x) {\012 // its safe to moveint i = 0;here\012 for (int n = 0; n < 10; ++n) {\012 // it is possible but not safe to moveint i = 0;` here\012 do_something(&i);\012 }\012 }\012}\012When you see this message it is always safe to reduce the variable scope 1 level. (detailed CWE explanation)
The scope of the variable utmp_id can be reduced. Warning: Be careful when fixing this message, especially when there are inner loops. Here is an example where cppcheck will write that the scope for i can be reduced:\012void f(int x)\012{\012 int i = 0;\012 if (x) {\012 // its safe to moveint i = 0;here\012 for (int n = 0; n < 10; ++n) {\012 // it is possible but not safe to moveint i = 0;` here\012 do_something(&i);\012 }\012 }\012}\012When you see this message it is always safe to reduce the variable scope 1 level. (detailed CWE explanation)