Debugging programs c

Question

Programming is in a sense easy. But mistakes are what always cause more problems. Can someone help me with some good debugging tricks and tools in c?

Answer 1

Popular debugging tools are listed below.

• Valgrind
• Purify
• Duma

Some very simple tricks / suggestions

-> Always check that nowhere in your code have you dereferenced a wild / sagging pointer

Example 1)

int main()
{
     int *p;
     *p=10; //Undefined Behaviour (crash on most implementations)
}

Example 2)

int main()
{

     int *p=malloc(sizeof(int));
     //do something with p

     free p;
     printf("%d", *p); ////Undefined Behaviour (crash on most implementations)
}

-> Always initialize variables before use

 int main()
  {

    int k;

    for(int i= k;i<10;++i)
              ^^
            Ouch
      printf("%d",i");
  }

Answer 2

From "Elements of a Programming Style," Brian Kernigan, 2nd Edition, Chapter 2:

, . , , , , - ?

, ; " "!

, ; ! . , , , .

, ; . , lint, pclint QA-C, .

Answer 3

, . , , - , . :

• , , . C 25 - .
• . , , .
• . , , .
• . , , , . , ( ), , .
• - . , .

, , , , , !

Answer 4

C

• GDB

:

• Valgrind

Answer 5

. .

Answer 6

• gdb - .
• printf
• Valgrind
• . - .

Answer 7

:

:

• ,
• .
• ,

-

• /
• .
• .

Answer 8

(gdb, valgrind, ), .

• . ( size_t) , , ptrdiff_t , off_t .. enum .
• int, long, char . , .
• , char , - . uint8_t int8_t .
• , : integer, double, , struct. , . , . , . NULL , .
• , . .
• , , .
• assert. , , .

Answer 9

, .

Answer 10

, David Agans. .

Answer 11

valgrind , Linux. gdb/ddd linux. , , windbg. , , ​​ gdb; , . assert, , , . , ​​ Check, cunit .. NULL, . , NULL. segfault, . , . , , 10 , . gcc -Wall -Wextra. strn * str *. , .