Skip to content
  1. Sep 23, 2017
  2. Sep 21, 2017
  3. Sep 09, 2017
  4. Sep 08, 2017
  5. Sep 07, 2017
  6. Sep 06, 2017
  7. Sep 05, 2017
    • Eric Bruneton's avatar
      Fix the computation of the Label.DEBUG flag. · aa6ca893
      Eric Bruneton authored
      The current code can incorrectly classify a Label as "used only for debug", which can yield incorrect stack map offsets due to skipped labels in MethodWriter.visitLabel (see bug #317791). This happens when a label is found for the first time in a debug attribute (it is then flagged as DEBUG), and then appears again in a stack map frame (these labels are extracted after those from the debug attributes, during the bytecode parsing, but the DEBUG flag, if present, is not removed then).
      
      The fix consists in removing the DEBUG flag, if present, when creating or reusing a label for non-debug attributes.
      aa6ca893
  8. Sep 03, 2017
  9. Sep 02, 2017
  10. Jul 23, 2017
  11. Jul 16, 2017
  12. Jul 05, 2017
  13. Jun 24, 2017
  14. Jun 05, 2017
  15. Jun 04, 2017
  16. Feb 11, 2017
  17. Feb 05, 2017
  18. Aug 27, 2016
  19. Aug 15, 2016
  20. Apr 24, 2016