1 <!-- Copyright (C) 2003 Red Hat, Inc. -->
2 <!-- This material may be distributed only subject to the terms -->
3 <!-- and conditions set forth in the Open Publication License, v1.0 -->
4 <!-- or later (the latest version is presently available at -->
5 <!-- http://www.opencontent.org/openpub/). -->
6 <!-- Distribution of the work or derivative of the work in any -->
7 <!-- standard (paper) book form is prohibited unless prior -->
8 <!-- permission is obtained from the copyright holder. -->
12 >Default Synchronous Exception Handling</TITLE
13 ><meta name="MSSmartTagsPreventParsing" content="TRUE">
16 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
19 TITLE="eCos Reference Manual"
20 HREF="ecos-ref.html"><LINK
22 TITLE="Exception Handling"
23 HREF="hal-exception-handling.html"><LINK
25 TITLE="Vectors and VSRs"
26 HREF="hal-vectors-and-vsrs.html"><LINK
28 TITLE="Default Interrupt Handling"
29 HREF="hal-default-interrupt-handling.html"></HEAD
40 SUMMARY="Header navigation table"
49 >eCos Reference Manual</TH
57 HREF="hal-vectors-and-vsrs.html"
65 >Chapter 10. Exception Handling</TD
71 HREF="hal-default-interrupt-handling.html"
85 NAME="HAL-DEFAULT-SYNCHRONOUS-EXCEPTION-HANDLING">Default Synchronous Exception Handling</H1
87 >Most synchronous exception VSR table entries will point to a default
88 exception VSR which is responsible for handling all exceptions in a
89 generic manner. The default VSR simply saves the CPU state, makes any
90 adjustments to the CPU state that is necessary, and calls
93 >cyg_hal_exception_handler()</TT
98 >cyg_hal_exception_handler()</TT
100 exception on to some handling code. There are two basic destinations:
101 enter GDB or pass the exception up to eCos. Exactly which
102 destination is taken depends on the configuration. When the GDB stubs are
103 included then the exception is passed to them, otherwise it is passed
106 >If an eCos application has been loaded by RedBoot then the VSR table
107 entries will all point into RedBoot's exception VSR, and will
108 therefore enter GDB if an exception occurs. If the eCos application
109 wants to handle an exception itself, it needs to replace the the VSR
110 table entry with one pointing to its own VSR. It can do this with the
113 >HAL_VSR_SET_TO_ECOS_HANDLER()</TT
121 SUMMARY="Footer navigation table"
132 HREF="hal-vectors-and-vsrs.html"
150 HREF="hal-default-interrupt-handling.html"
160 >Vectors and VSRs</TD
166 HREF="hal-exception-handling.html"
174 >Default Interrupt Handling</TD