[RTEMS Project] #4459: Handling of unexpected traps is unreliable on SPARC

[RTEMS trac]

#4459: Handling of unexpected traps is unreliable on SPARC
-----------------------------+------------------------------
 Reporter:  Sebastian Huber  |       Owner:  Sebastian Huber
     Type:  defect           |      Status:  assigned
 Priority:  normal           |   Milestone:
Component:  arch/sparc       |     Version:  6
 Severity:  normal           |  Resolution:
 Keywords:  qualification    |  Blocked By:
 Blocking:                   |
-----------------------------+------------------------------

Comment (by Sebastian Huber <sebastian.huber@…>):

 In [changeset:"d73e657e063e3d34db16fa4bce6c2ab1e5e22ec4/rtems"
 d73e657e/rtems]:
 {{{
 #!CommitTicketReference repository="rtems"
 revision="d73e657e063e3d34db16fa4bce6c2ab1e5e22ec4"
 sparc: More reliable bad trap handling

 Statically initialize the trap table in start.S to jump to
 _SPARC_Bad_trap()
 for all unexpected traps.  This enables a proper RTEMS fatal error
 handling
 right from the start.  Do not rely on the stack and register settings
 which
 caused an unexpected trap.  Use the ISR stack of the processor to do the
 fatal
 error handling.  Save the full context which caused the trap.  Fatal error
 handler may use it for error logging.

 Unify the _CPU_Exception_frame_print() implementations and move it to
 cpukit.

 Update #4459.
 }}}

--
Ticket URL: <http://devel.rtems.org/ticket/4459#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project