Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
DrawFile DrawFile
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • RiscOS
    • SSources
    • VVideo
  • Render
  • DrawFileDrawFile
  • Merge requests
  • !3

Merged
Created Jul 12, 2022 by Robert Sprowson@rsprowsonDeveloper

[541] Fix for returning a stale error pointer

  • Overview 0
  • Commits 1
  • Changes 2

During the rendering process (or Service_DrawObjectRender for unknown objects) the render state may be updated with an error pointer. However, as rending proceeds and potentially many other SWIs are called also using MessageTrans' shared buffers, by the end of the rendering process the originally captured pointer may be pointing at a totally different message. Capture the error after each object is despatched in our own buffer.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: bug-541