Changes between Version 12 and Version 13 of Debugging/GDBScripts


Ignore:
Timestamp:
Jan 5, 2016, 7:43:36 PM (4 years ago)
Author:
Ralph Holmes
Comment:

Fix broken link(s).

Legend:

Unmodified
Added
Removed
Modified
  • Debugging/GDBScripts

    v12 v13  
    1 = GdbScripts =
    2 
     1= GDBScripts =
    32
    43This is a set of user-defined commands for gdb which are useful in analyzing an RTEMS application. They can be used to display information about a number of RTEMS objects classes along with information about the system in general.  The user defined commands should be saved in a file which is "sourced" as part of invoking gdb.  This can be done in two ways. The first is from the command line:
     
    2726 
    2827Changed the variable named $count to $i (don't know why I needed to do this)
    29 Adjusted the stack backtrace for Coldfire ( use frame pointer a6 as the starting
    30 point for the back trace).
     28Adjusted the stack backtrace for Coldfire (use frame pointer a6 as the starting point for the back trace).
    3129
    3230--Paul Whitfield 19:25, 6 Aug 2006 (CDT)
     
    3432----
    3533
    36 Moved out of the Wiki to the FTP server and updated for RTEMS 4.9. Check out http://www.rtems.org/ftp/pub/rtems/people/chrisj/gdb-scripts.
     34Moved out of the Wiki to the FTP server and updated for RTEMS 4.9. Check out https://ftp.rtems.org/pub/rtems/people/chrisj/gdb/scripts/.
    3735
    3836Add support for the i386. You need to edit the script file to get back trace support for your target.
     
    4240--- Using GDB Commands
    4341
    44 As described load the commands into GDB. You can use the command line used to invoke GDB, the GDB command or they can be placed in a GDB script. There currently is no standard to keep this script so I have placed it in my FTP area on the RTEMS FTP server. The link it:
     42As described load the commands into GDB. You can use the command line used to invoke GDB, the GDB command or they can be placed in a GDB script. There currently is no standard to keep this script so I have placed it in my FTP area on the RTEMS FTP server. The link is:
    4543
    46 http://www.rtems.org/ftp/pub/rtems/people/chrisj/gdb-scripts
     44https://ftp.rtems.org/pub/rtems/people/chrisj/gdb/scripts/
    4745
    4846Please send patches to the RTEMS user list.
     47
    4948= Check Status =
    5049
    51 
    5250You will typically come to this page when you have a problem with an application or driver and you are struggling to find a solution. I had one such problem just recently. I had a mutex that once a task blocked on all tasks at the same priority or lower stopping running except IDLE. The {{{rtems_check_state</code> showed IDLE was not at its normal priority and a priority inversion bug relating to creating locked semaphores was shown to be problem. So first run this command to make sure you are not doing something that is know about.