Last Updated: 11/14/2017
A non-map break occurs in the debugger and the program execution stops. No error in particular occurs in the compiler and linker. What causes this non-map error and what is the countermeasure?
It is not possible to tell based solely on this information. If a non-map break occurs and program execution stops, that the data used to access problematic non-mapped areas should remain in the trace data. Please check whether this is really access to memory other than the relevant memory.