Changes between Version 5 and Version 6 of Docs/Prog/Manual/Debugging


Ignore:
Timestamp:
11/30/09 10:48:27 (15 years ago)
Author:
Don Wilson
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Docs/Prog/Manual/Debugging

    v5 v6  
    11[[TOC(heading=Table of Contents, Docs/Prog/Manual/*)]]
    2 = Debugging =
    3 == GDB ==
    4 
    5 GDB is an open source debugger that is included in the !CodeSourcery development package.
    6 
    7 Using a terminal program such as Hyperterm to communicate with the 825 console at the “#” prompt type:
    8 
    9 gdbserver :''port'' ''progname'' [''args''] &  (where port is the TCP/IP port to be used, and programe is the name of the program to be debugged)
    10 
    11 For example:
    12 
    13 gdbserver :10000 cardbas 788IDS.77X &
    14 
    15 This will start the gdbserver process:
    16 
    17 184
    18 
    19 Process cardbas created; pid = 185
    20 
    21 Listening on port 10000
    22 
    23 From the PC you may then start debugging by selecting the “Debug” perspective and then clicking the “Bug” icon in Eclipse.
    24 
    25 For example, the terminal will show:
    26 
    27 Remote debugging from host 90.1.1.216
    28 
    29 Breakpoints may be set by double-clicking the border just to the left of a program line in the editor.
    30 
    31 F5 – Step Into (If stopped at a function call, this will step into the function)
    32 
    33 F6 – Step Over (If stopped at a function call, this will step over to the next statement)
    34 
    35 F8 – Resume (If stopped this will resume running)
    36 
    37 The “Variables” window will automatically show the local variables that are in use.
    38 
    39 Right-click in the “Variables” window and select “Add global Variables…” to select global variables to monitor. These will not appear until the next break.
    40 
    41 To stop the debugging session from !CodeSourcery click the red square icon. The application being debugged and the gdbserver will automatically exit.
    42 
    43 The terminal window will show:
    44 
    45 Killing inferior
    46 
    47 It is also possible to set gdbserver to attach to an already executing process.
    48 
    49 Determine the existing process ID first by using the PS command.
    50 
    51 gdbserver :''port'' – attach ''pid'' &  (where ''port ''is the TCP/IP port number and ''pid ''is the process ID)
    52 
    53 For example:
    54 
    55 gdbserver :10000 –attach 187 &
    56 
    57 When using the attach method stopping the debugging session from Eclipse may not stop gdbserver or the application.