Currently the thrown exceptions do not have any extra information available and on cannot really figure out, what (bitmap, text, layout...) has failed and where exactly (function, params?).

Considering deployed systems, debugging in case of an exception, there are very few clues to what exactly happened. Stepping in debug version is current way of figuring out, what happens, but that cannot be used in deployed vehicles that might have some sporadic problem. So a log memory and or API to car's / device's own logging system should be considered.