Remote Debugging with GDB - Revision history

Searchworks: remove spam

2010-11-23T23:02:00Z

remove spam

Aqisecoxefi at 22:37, 23 November 2010

2010-11-23T22:37:05Z

JustinC474: /* More Tutorial */

2010-08-06T16:54:17Z

‎More Tutorial

JustinC474: /* Using Backtrace */

2010-08-06T16:52:02Z

‎Using Backtrace

JustinC474: /* Stepping into a function */

2010-08-06T16:44:39Z

‎Stepping into a function

JustinC474: /* Stepping into a function */

2010-08-06T16:44:09Z

‎Stepping into a function

JustinC474: /* Setting a Breakpoint */

2010-08-06T16:40:52Z

‎Setting a Breakpoint

JustinC474 at 16:32, 6 August 2010

2010-08-06T16:32:33Z

JustinC474 at 16:20, 6 August 2010

2010-08-06T16:20:23Z

Ashcharles at 23:40, 4 August 2010

2010-08-04T23:40:05Z

@@ Line 1: / Line 1: @@
 In this tutorial we will go over how to perform a basic debugging with GDB, the GNU debugger. This environment allows us to debug C, C++ and Java (compiled to machine code, not for running in a Java Virtual Machine) programs.
 *We will complete these tasks step by step
@@ Line 44: / Line 36: @@
   nano broken.cpp
 Then copy and paste the code from [http://cs.baylor.edu/~donahoo/tools/gdb/broken.cpp |Broken.cpp] into your shell. When you copy and paste there will be two syntax errors that you must fix at the lines:
-  cout &lt;&lt; &quot;This program is used to compute the value of the following
+  cout << "This program is used to compute the value of the following
-  series : &quot; &lt;&lt; endl;
+  series : " << endl;
 and
-  cout &lt;&lt; &quot;(x^0)/0! + (x^1)/1! + (x^2)/2! + (x^3)/3! + (x^4)/4! + ....
+  cout << "(x^0)/0! + (x^1)/1! + (x^2)/2! + (x^3)/3! + (x^4)/4! + ....
-  .... + (x^n)/n! &quot; &lt;&lt; endl
+  .... + (x^n)/n! " << endl
 Copying and pasting added an extra line break to these two lines, and we want to undo this by deleting one space at the beginning of each second line so it looks like this:
-  cout &lt;&lt; &quot;This program is used to compute the value of the following series : &quot; &lt;&lt; endl;
+  cout << "This program is used to compute the value of the following series : " << endl;
 and
-  cout &lt;&lt; &quot;(x^0)/0! + (x^1)/1! + (x^2)/2! + (x^3)/3! + (x^4)/4! + ........ + (x^n)/n! &quot; &lt;&lt; endl
+  cout << "(x^0)/0! + (x^1)/1! + (x^2)/2! + (x^3)/3! + (x^4)/4! + ........ + (x^n)/n! " << endl
 Now save and exit by pressing the following:
 :*Ctrl + O
-:*&lt;Enter&gt;
+:*<Enter>
 :*Ctrl + X
@@ Line 106: / Line 98: @@
 However, for the purpose of this tutorial, use the line number. If you wish, you can play around with using the function instead, but it will cause you to diverge from this tutorial.
-If the program outputs: No symbol table is loaded.  Use the &quot;file&quot; command. Then use the following command:
+If the program outputs: No symbol table is loaded.  Use the "file" command. Then use the following command:
   (gdb) file broken
 This will set the file so that you can add a breakpoint without error
@@ Line 136: / Line 128: @@
 ----
 Hint:
-A nice thing about the GDB Debugger is that it will save the last command you issued so that you don't need to type it over and over. This way you can keep stepping through the function by pressing &lt;enter&gt;. You do not need to retype 'step' &lt;br&gt;
+A nice thing about the GDB Debugger is that it will save the last command you issued so that you don't need to type it over and over. This way you can keep stepping through the function by pressing <enter>. You do not need to retype 'step' <br>
 Hint:
 The GDB Debugger also has nice 'shortcuts'. For example, 'step' and 's' are the same command. So is 'breakpoint' and 'b'.
@@ Line 148: / Line 140: @@
   (gdb) next
   double xpow=1;
-  (gdb) &lt;enter&gt;
+  (gdb) <enter>
-  for (int k = 0; k &lt;= n; k++) {
+  for (int k = 0; k <= n; k++) {
-  (gdb) &lt;enter&gt;
+  (gdb) <enter>
     seriesValue += xpow / ComputeFactorial(k) ;
   (gdb) step
@@ Line 164: / Line 156: @@
 ----
 Hint:
-Backtrace lets you see where you have been and what you have done. In case, you get lost or confused it is very useful. &lt;br&gt;
+Backtrace lets you see where you have been and what you have done. In case, you get lost or confused it is very useful. <br>
 Hint:
-A stack is a data structure in Computer Science which stores data much like a stack of cards. It is a Last On, First Off data structure. For more explanation of how a stack functions, see the wikipedia article. &lt;br&gt;
+A stack is a data structure in Computer Science which stores data much like a stack of cards. It is a Last On, First Off data structure. For more explanation of how a stack functions, see the wikipedia article. <br>
 http://en.wikipedia.org/wiki/Stack_(data_structure)
 ----

@@ Line 1: / Line 1: @@
 In this tutorial we will go over how to perform a basic debugging with GDB, the GNU debugger. This environment allows us to debug C, C++ and Java (compiled to machine code, not for running in a Java Virtual Machine) programs.
 *We will complete these tasks step by step
@@ Line 36: / Line 44: @@
   nano broken.cpp
 Then copy and paste the code from [http://cs.baylor.edu/~donahoo/tools/gdb/broken.cpp |Broken.cpp] into your shell. When you copy and paste there will be two syntax errors that you must fix at the lines:
-  cout << "This program is used to compute the value of the following
+  cout &lt;&lt; &quot;This program is used to compute the value of the following
-  series : " << endl;
+  series : &quot; &lt;&lt; endl;
 and
-  cout << "(x^0)/0! + (x^1)/1! + (x^2)/2! + (x^3)/3! + (x^4)/4! + ....
+  cout &lt;&lt; &quot;(x^0)/0! + (x^1)/1! + (x^2)/2! + (x^3)/3! + (x^4)/4! + ....
-  .... + (x^n)/n! " << endl
+  .... + (x^n)/n! &quot; &lt;&lt; endl
 Copying and pasting added an extra line break to these two lines, and we want to undo this by deleting one space at the beginning of each second line so it looks like this:
-  cout << "This program is used to compute the value of the following series : " << endl;
+  cout &lt;&lt; &quot;This program is used to compute the value of the following series : &quot; &lt;&lt; endl;
 and
-  cout << "(x^0)/0! + (x^1)/1! + (x^2)/2! + (x^3)/3! + (x^4)/4! + ........ + (x^n)/n! " << endl
+  cout &lt;&lt; &quot;(x^0)/0! + (x^1)/1! + (x^2)/2! + (x^3)/3! + (x^4)/4! + ........ + (x^n)/n! &quot; &lt;&lt; endl
 Now save and exit by pressing the following:
 :*Ctrl + O
-:*<Enter>
+:*&lt;Enter&gt;
 :*Ctrl + X
@@ Line 98: / Line 106: @@
 However, for the purpose of this tutorial, use the line number. If you wish, you can play around with using the function instead, but it will cause you to diverge from this tutorial.
-If the program outputs: No symbol table is loaded.  Use the "file" command. Then use the following command:
+If the program outputs: No symbol table is loaded.  Use the &quot;file&quot; command. Then use the following command:
   (gdb) file broken
 This will set the file so that you can add a breakpoint without error
@@ Line 128: / Line 136: @@
 ----
 Hint:
-A nice thing about the GDB Debugger is that it will save the last command you issued so that you don't need to type it over and over. This way you can keep stepping through the function by pressing <enter>. You do not need to retype 'step' <br>
+A nice thing about the GDB Debugger is that it will save the last command you issued so that you don't need to type it over and over. This way you can keep stepping through the function by pressing &lt;enter&gt;. You do not need to retype 'step' &lt;br&gt;
 Hint:
 The GDB Debugger also has nice 'shortcuts'. For example, 'step' and 's' are the same command. So is 'breakpoint' and 'b'.
@@ Line 140: / Line 148: @@
   (gdb) next
   double xpow=1;
-  (gdb) <enter>
+  (gdb) &lt;enter&gt;
-  for (int k = 0; k <= n; k++) {
+  for (int k = 0; k &lt;= n; k++) {
-  (gdb) <enter>
+  (gdb) &lt;enter&gt;
     seriesValue += xpow / ComputeFactorial(k) ;
   (gdb) step
@@ Line 156: / Line 164: @@
 ----
 Hint:
-Backtrace lets you see where you have been and what you have done. In case, you get lost or confused it is very useful. <br>
+Backtrace lets you see where you have been and what you have done. In case, you get lost or confused it is very useful. &lt;br&gt;
 Hint:
-A stack is a data structure in Computer Science which stores data much like a stack of cards. It is a Last On, First Off data structure. For more explanation of how a stack functions, see the wikipedia article. <br>
+A stack is a data structure in Computer Science which stores data much like a stack of cards. It is a Last On, First Off data structure. For more explanation of how a stack functions, see the wikipedia article. &lt;br&gt;
 http://en.wikipedia.org/wiki/Stack_(data_structure)
 ----

@@ Line 174: / Line 174: @@
 ==More Tutorial==
-For another tutorial see:
+For another tutorial which is more in depth, see:
 http://www.cs.cmu.edu/~gilpin/tutorial/

@@ Line 155: / Line 155: @@
   #2  0x08048a31 in main () at broken.cpp:43
 ----
-Note:
+Hint:
-Backtrace lets you see where you have been and what you have done. In case, you get lost or confused it is very useful.
+Backtrace lets you see where you have been and what you have done. In case, you get lost or confused it is very useful. <br>
 ----
 See the error?

@@ Line 128: / Line 128: @@
 ----
 Hint:
-A nice thing about the GDB Debugger is that it will save the last command you issued so that you don't need to type it over and over. This way you can keep stepping through the function by pressing <enter>. You do not need to retype 'step'
+A nice thing about the GDB Debugger is that it will save the last command you issued so that you don't need to type it over and over. This way you can keep stepping through the function by pressing <enter>. You do not need to retype 'step' <br>
 Hint:
 The GDB Debugger also has nice 'shortcuts'. For example, 'step' and 's' are the same command. So is 'breakpoint' and 'b'.

@@ Line 129: / Line 129: @@
 Hint:
 A nice thing about the GDB Debugger is that it will save the last command you issued so that you don't need to type it over and over. This way you can keep stepping through the function by pressing <enter>. You do not need to retype 'step'
 ----
 You should see the following outputted:

@@ Line 94: / Line 94: @@
 Lets set a breakpoint within the program so that we can see what is going on. Lets start by setting a breakpoint at line 43. Do this with the following command:
   (gdb) b 43
-----
+You could also set a breakpoint to a specific functions call, such as:
-Note:
+ (gdb) b ComputeSeriesValue
 If the program outputs: No symbol table is loaded.  Use the "file" command. Then use the following command:
   (gdb) file broken
 This will set the file so that you can add a breakpoint without error
-----
 Line 43 is the following:
   double seriesValue = ComputeSeriesValue(x, n);
@@ Line 114: / Line 116: @@
   Breakpoint 1, main () at broken.cpp:43
   double seriesValue = ComputeSeriesValue(x, n);
 The program has stopped at our breakpoint, line 43.
 ===Stepping into a function===

@@ Line 20: / Line 20: @@
 ==Installing the GDB Debugger==
 Before starting this, you should have Console access to your Overo COM and should know how to program and run a basic C++ program. If you do not know how to do this, see [[HelloWorld | HelloWorld in Python, C and C++]].
 To install the GDB debugger, run the following command in your command line:

@@ Line 1: / Line 1: @@
-In this tutorial we will go over how to perform a basic debugging with GDB, the GNU debugger. This environment allows us to debug machine code. You will not be able to debug java programs with this unless you find a way to compile you java file into an executable that does not require a Java Virtual Machine.
+In this tutorial we will go over how to perform a basic debugging with GDB, the GNU debugger. This environment allows us to debug C, C++ and Java (compiled to machine code, not for running in a Java Virtual Machine) programs.
 *We will complete these tasks step by step
-:*Installing the GDB debugger
+:*Install the GDB debugger
-:*Running the debugger
+:*Run the debugger
-:*Learn how to set Breakpoints
+:*Set Breakpoints
-:*Learn how to navigate the code in your program
+:*Navigate the code in your program
-:*Learn how to diagnose an error and how to fix it
+:*Diagnose an error and how to fix it
 *Required Items
@@ Line 16: / Line 16: @@
 :*[[HelloWorld | HelloWorld in Python, C and C++]]
 :*[[Eclipse on Gumstix for new users | Eclipse Tutorial]]
-::*Although the majority of this tutorial regards Eclipse and Java programming, it contains useful information which leads to basic understanding of your Overo COM
+::*Although the majority of this tutorial pertains to debugging and C programming, it contains useful information which leads to basic understanding of your Overo COM
 ==Installing the GDB Debugger==
@@ Line 53: / Line 53: @@
 Compile the program to create an executable file (broken) by entering the following command:
   g++ -g broken.cpp -o broken
-Then run it:
+The '-g' switch tells the compiler to include debugging symbols in the executable. Run the program as such:
   ./broken
 ----
@@ Line 148: / Line 148: @@
 ----
 Note:
-Backtrace lets you see where you have been and what you have done, in the case you get lost or confused it is very useful.
+Backtrace lets you see where you have been and what you have done. In case, you get lost or confused it is very useful.
 ----
 See the error?
@@ Line 160: / Line 160: @@
 to
   int fact =1;
-and your all set!
+and you're all set!
 For another tutorial see:
 http://www.cs.cmu.edu/~gilpin/tutorial/