1. 24 Sep, 2017 1 commit
  2. 06 Jul, 2016 1 commit
  3. 18 Sep, 2015 1 commit
  4. 06 May, 2015 1 commit
  5. 01 Nov, 2014 1 commit
  6. 20 Sep, 2014 1 commit
  7. 10 Jun, 2014 2 commits
  8. 09 Jun, 2014 2 commits
    • Robin Watts's avatar
      Bug 695300: Sanitize draw-device stack handling in error cases. · fdea617e
      Robin Watts authored
      When throwing an error during fz_alpha_from_gray, the stack depth
      can get confused. Fix this by moving some more code into the
      appropriate fz_try().
      
      In the course of fixing this bug, I added some new optional debug
      code to display the stack level as it runs. This is committed here
      disabled; just change the appropriate #define in draw-device.c to
      enable it.
      
      Also, add some code to run_xobject, to avoid throwing in an fz_always()
      clause.
      fdea617e
    • Tor Andersson's avatar
      Fix 695300: don't throw exception on invalid reference number. · a6f0d56d
      Tor Andersson authored
      Return the null object rather than throwing an exception when parsing
      indirect object references with negative object numbers.
      
      Do range check for object numbers (1 .. length) when object numbers
      are used instead.
      
      Object number 0 is not a valid object number. It must always be 'free'.
      a6f0d56d
  9. 29 May, 2014 2 commits
  10. 28 May, 2014 3 commits
  11. 27 May, 2014 5 commits
  12. 26 May, 2014 2 commits
    • Robin Watts's avatar
      Bug 695260: Fix error handling in do_xobject · 0c041d7f
      Robin Watts authored
      Various functions (such as fz_begin_group) handle errors internally
      by use of the error_depth parameter. This means that if we call
      them, we MUST ensure that we call the appropriate closing function.
      Similarly, if we don't call them, we should NOT call the closing
      function.
      
      In order to ensure we do this correctly, we introduce a cleanup_state
      variable that says which ones we tried to call.
      
      This cures the original bug.
      0c041d7f
    • Tor Andersson's avatar
      Fix 695261: separate TM and CTM in outline extraction and stroking steps. · 253a976a
      Tor Andersson authored
      We used to extract the outline using the combined TM*CTM matrix and
      use the identity transform for stroking, thus ending up with the wrong
      line width.
      
      If we instead extract using the TM and then stroke with the CTM we get
      the correct results.
      253a976a
  13. 23 May, 2014 3 commits
  14. 22 May, 2014 5 commits
  15. 20 May, 2014 1 commit
  16. 19 May, 2014 4 commits
  17. 15 May, 2014 1 commit
  18. 13 May, 2014 2 commits
  19. 12 May, 2014 2 commits