Changes between Version 9 and Version 10 of Debugging/GDBScripts


Ignore:
Timestamp:
Jul 25, 2008, 2:41:48 AM (11 years ago)
Author:
ChrisJohns
Comment:

Add check status.

Legend:

Unmodified
Added
Removed
Modified
  • Debugging/GDBScripts

    v9 v10  
    2929Adjusted the stack backtrace for Coldfire ( use frame pointer a6 as the starting
    3030point for the back trace).
     31
    3132--[wiki:User:Paulwhitfield Paul Whitfield] 19:25, 6 Aug 2006 (CDT)
    3233
     
    3839
    3940--[wiki:User:ChrisJohns ChrisJohns] 07:00, 22 July 2008 (CDT)
     41
     42--- Using GDB Commands
     43
     44As 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:
     45
     46http://www.rtems.org/ftp/pub/rtems/people/chrisj/gdb-scripts
     47
     48Please send patches to the RTEMS user list.
     49= Check Status =
     50
     51
     52You 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.