Uploaded image for project: 'Qt Safe Renderer'
  1. Qt Safe Renderer
  2. QSR-642

Make an API/a mechanism to record detailed errors during runtime

    XMLWordPrintable

Details

    • Epic
    • Resolution: Unresolved
    • Not Evaluated
    • None
    • None
    • Documentation, Runtime, Testing
    • None

    Description

      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.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              qtsaferendererteam Qt Safe Renderer Team
              jani.launonen Jani Launonen (Inactive)
              Veli-Pekka Heinonen Veli-Pekka Heinonen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes