Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Changes between Version 14 and Version 15 of TBR/Review/Debugging/Start


Ignore:
Timestamp:
08/17/07 15:19:53 (17 years ago)
Author:
JoelSherrill
Comment:

/* NOTES */ Clarify why it faulted -- printf

Legend:

Unmodified
Added
Removed
Modified
  • TBR/Review/Debugging/Start

    v14 v15  
    433433
    434434#Stack usage information is questionable on CPUs which push large holes on stack.
    435 #The stack checker has a tendency to generate a fault when trying to print the helpful diagnostic message.  If it comes out, congratulations. If not, then the variable Stack_check_Blown_task contains a pointer to the TCB of the offending task.  This is usually enough to go on.
     435#Prior to 4.7.99.2, the stack checker used printf() instead of printk().  This often resulted in a fault when trying to print the helpful diagnostic message.  If using the older printf() stack checker and it comes out, congratulations. If not, then the variable Stack_check_Blown_task contains a pointer to the TCB of the offending task.  This is usually enough to go on.  Now that it is using printk(), it should be able to get messages out.
    436436=  = FUTURE ====
    437437