What If the Hardware Architecture, Software Architecture, or Mapping Dynamic Libraries Crash?
tejacc gets information about hardware architecture, software architecture, and mapping by executing the configuration code compiled into dynamic libraries. The code is written in C and might contain errors causing tejacc to crash. Upon crashing, you are presented with a Java Hotspot exception, as tejacc is internally implemented in Java. An alternative version of tejacc.sh called tejacc_dbg.sh is provided to assist debugging configuration code. This program runs tejacc inside the default host debugger (gdb for Linux/Cygwin hosts, dbx for Solaris hosts). The execution automatically stops immediately after the hardware architecture, software architecture, and mapping dynamic libraries have been loaded by tejacc. You can continue the execution and the debugger stops at the instruction causing the crash. Alternatively, you can set breakpoints in the code before continuing or use any other feature provided by the host debugger.
Related Questions
- Does the municipal digital parcel mapping grant require previous investment in hardware and software? Can we approach neighboring towns and increase our purchasing power?
- Can I Build Hardware Architecture, Software Architecture, and Mapping in the Same Dynamic Library?
- What If the Hardware Architecture, Software Architecture, or Mapping Dynamic Libraries Crash?
