• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            EverSpring working shop

            To pursue creative ideas based on nature.

            統計

            留言簿(1)

            他山之石

            閱讀排行榜

            評論排行榜

            GDB Tutorial for beginners (From network, i am reading also.)

            QUOTE

                  The  purpose  of a debugger such as GDB is to allow you to see what is
                  going on ‘‘inside’’ another program while it executes—or what  another
                  program was doing at the moment it crashed.
                                                                                           
                  GDB  can do four main kinds of things (plus other things in support of
                  these) to help you catch bugs in the act:
                                                                                           
                      ·  Start your program, specifying anything that might  affect  its
                          behavior.
                                                                                           
                      ·  Make your program stop on specified conditions.
                                                                                           
                      ·  Examine what has happened, when your program has stopped.
                                                                                           
                      ·  Change  things in your program, so you can experiment with cor-
                          recting the effects of  one  bug  and  go  on  to  learn  about
                          another.
            --GDB Manpage


            The first thing you need to do to start debugging your program is to compile it with debugging symbols, this is accomplished with the -g flag:
            gcc filename.c -g -o filename
            g++ filename.cpp -g -o filename


            Lets start with a simple program that gets a line of text from the user, and prints it out backwards to the screen:


            CODE

            #include <stdio.h>
                                                                                                                                                                         
            int main(){

            char input[50];
            int i=0;

            scanf("%s",input);

            for(i=strlen(input);i>=0;i--)
               { printf("%c",input[i]);}
            printf("\n");

            return 0;
            }



            compile and start the debugger with:
            gcc -g debug.c
            gdb ./a.out

            You should now be in the debugger.


            There are 8 main commands that you will mostly be using in your debugging session

            1.) break
            2.) run
            3.) print
            4.) next
            5.) step
            6.) continue
            7.) display
            8.) where



            1.) The Break Command:
            gdb will remeber the line numbers of your source file. This will let us easily set up break points in the program. A break point, is a line in the code where you want execution to pause. Once you pause execution you will be able to examine variables, and walk through the program, and other things of that nature.
            Continueing with our example lets set up a break point at line 6, just before we declare int i=0;

            QUOTE

            (gdb) break 6
            Breakpoint 1 at 0x80483ec: file debug.c, line 6.
            (gdb)




            2.) The Run Command
            Run will begin inital execution of your program. This will run your program as you normally would outside of the debugger, until it reaches a break point line.
            At this moment, you will have been returned to the gdb command prompt.
            (Using run again after your prgram has been started, will ask to terminate the current execution and start over)

            From our example:

            QUOTE

            (gdb) run
            Starting program: /u/khan/tmp/a.out
                                                                                           
            Breakpoint 1, main () at debug.c:6
            6      int i=0;
            (gdb)



            3.)The Print Command
            Print will let you see the values of data in your program. It takes an argument of the variable name.
            In our example, we are paused right before we declare and intitalize i. Lets look what the value of i is now:

            QUOTE

            (gdb) print i
            $1 = -1075457232
            (gdb)


            i contains junk, we havent put anything into it yet.


            4. & 5.) Next and Step
            Next and Step do basically the same thing, step line by line through the program. The difference is that next steps over a function call, and step will step into it.

            Now in our example, we will step to the beginning of the next instruction

            QUOTE

            (gdb) step
            8      scanf("%s",input);
            (gdb)


            before we execute the scanf, lets check the value of i again:
            QUOTE
            (gdb) print i
            $2 = 0
            (gdb)


            i is now equal to 0, like it should be.

            Now lets use next to move into the scanf statement:
            QUOTE

            (gdb) next


            What happened here? We werent returned to the gdb prompt. Well the program is inside scanf, waiting for us to input something.
            Input string here, and press enter:


            6.) The Continue Command
            Continue will pick up execution of the program after it has reached a break point.

            Lets continue to the end of the program now:
            QUOTE

            (gdb) continue
            Continuing.
            tupni

            Program exited normally.
            (gdb)


            Here we've reached the end of our program, you can see that it printed in resevese "input" which was what I fed it in scanf.


            7.) The Display Command
            display will show a vaiables contents each step of the way in your program. Lets start over in our example. Delete the breakpoint at line 6
            QUOTE

            (gdb) del break 1

            This deletes our first breakpoint at line 6.

            Now lets set a new breakpoint at line 11, the printf statement inside the for loop
            QUOTE

            (gdb) break 11
            Breakpoint 3 at 0x8048421: file debug.c, line 11.
            (gdb)


            Run the program again, and enter the input, when it returns to the gdb command prompt we will display input[i] and watch it through the for loop

            QUOTE

            Breakpoint 3, main () at debug.c:11
            11      { printf("%c",input[i]);}
            (gdb) display input[i]
            1: input[i] = 0 '\0'
            (gdb) next
            10      for(i=strlen(input);i>=0;i--)
            1: input[i] = 0 '\0'
            (gdb) next

            Breakpoint 3, main () at debug.c:11
            11      { printf("%c",input[i]);}
            1: input[i] = 116 't'
            (gdb) next
            10      for(i=strlen(input);i>=0;i--)
            1: input[i] = 116 't'
            (gdb) next

            Breakpoint 3, main () at debug.c:11
            11      { printf("%c",input[i]);}
            1: input[i] = 117 'u'
            (gdb) next
            10      for(i=strlen(input);i>=0;i--)
            1: input[i] = 117 'u'
            (gdb) next

            Breakpoint 3, main () at debug.c:11
            11      { printf("%c",input[i]);}
            1: input[i] = 112 'p'
            (gdb) next
            10      for(i=strlen(input);i>=0;i--)
            1: input[i] = 112 'p'
            (gdb) next

            Breakpoint 3, main () at debug.c:11
            11      { printf("%c",input[i]);}
            1: input[i] = 110 'n'
            (gdb) next
            10      for(i=strlen(input);i>=0;i--)
            1: input[i] = 110 'n'
            (gdb) next

            Breakpoint 3, main () at debug.c:11
            11      { printf("%c",input[i]);}
            1: input[i] = 105 'i'
            (gdb) next
            10      for(i=strlen(input);i>=0;i--)
            1: input[i] = 105 'i'
            (gdb) next
            12      printf("\n");
            1: input[i] = -1 '\uffff'
            (gdb)

            Here we stepped through the loop, always looking at what input[i] was equal to.


            9.)The Where Command
            The where command prints a backtrace of all stack frames. This may not make much since but it is useful in seeing where our program crashes.

            Lets modify our program just a little so that it will crash:
            CODE

            #include <stdio.h>
                                                                                                                                                                         
            int main(){

            char *input;
            int i=0;

            scanf("%s",input);

            for(i=strlen(input);i>=0;i--)
               { printf("%c",input[i]);}
            printf("\n");

            return 0;
            }


            Here we've changed input to be a pointer to a char.

            Recompile and run gdb on it again.

            and see what happens when it crashes

            QUOTE


            (gdb) r
            Starting program: /u/khan/tmp/a.out
            AAA

            Program received signal SIGSEGV, Segmentation fault.
            0x009ef267 in _IO_vfscanf_internal () from /lib/tls/libc.so.6
            (gdb) where
            #0  0x009ef267 in _IO_vfscanf_internal () from /lib/tls/libc.so.6
            #1  0x009f3808 in scanf () from /lib/tls/libc.so.6
            #2  0x08048403 in main () at debug.c:8
            (gdb)



            We see at the bottom, three frames,
            #2, the top most shows where we crashed at.

            use the up command to move up the stack
            QUOTE

            (gdb) up
            #1  0x009f3808 in scanf () from /lib/tls/libc.so.6
            (gdb) up
            #2  0x08048403 in main () at debug.c:8
            8      scanf("%s",input);
            (gdb)

            Here we see line #8
            8 scanf("%s",input);

            The line we crashed at.




            These are the basics to gdb, you can now find where a program crashed, watch variables, and step through line by line of your program.

            For more info check out the info page
            info gdb

            posted on 2007-10-12 22:02 everspring79 閱讀(856) 評論(0)  編輯 收藏 引用 所屬分類: Tools

            亚洲国产一成人久久精品| 66精品综合久久久久久久| 一级做a爰片久久毛片免费陪| 久久久久综合中文字幕| 色偷偷88888欧美精品久久久| 亚洲综合婷婷久久| 亚洲国产精品18久久久久久| 国产高潮久久免费观看| 性高湖久久久久久久久| 久久久综合香蕉尹人综合网| 色综合久久无码五十路人妻| 久久国产成人| 久久精品视频免费| 性欧美丰满熟妇XXXX性久久久| 国产精品青草久久久久福利99 | www亚洲欲色成人久久精品| 久久人妻AV中文字幕| 国产2021久久精品| 国产欧美一区二区久久| 久久久久久久久久久精品尤物 | 久久精品国产精品国产精品污| 国产精品久久久久久久久久影院| 蜜桃麻豆www久久| 亚洲国产精品18久久久久久| 久久国产精品无| 性高朝久久久久久久久久| 久久精品国产72国产精福利| 国产成人久久AV免费| 色综合久久综合中文综合网| 一本一本久久aa综合精品| 亚洲午夜久久久影院伊人| 久久精品aⅴ无码中文字字幕不卡| 久久精品国产72国产精福利| 久久免费视频6| 三级片免费观看久久| 伊人久久大香线蕉AV一区二区| 久久久久无码专区亚洲av| 色欲综合久久躁天天躁| 精品久久久久久无码不卡| 久久久久久久女国产乱让韩| 无码国产69精品久久久久网站|