Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8064516

BCEL still corrupts generic methods if bytecode offsets are modified

    XMLWordPrintable

Details

    • b40
    • generic
    • generic

    Backports

      Description

        Unfortunately, the fix for jdk8062608 does not go far enough. While jdk8062608 fixed the MethodGen constructor so that the LVT is no longer corrupted, and the LVTT is correctly duplicated when "cloning" a method, the rest of the MethodGen class still has no knowledge of the VLTT. So if we subsequently modify the instruction list, only bytecode offsets in the LVT are updated, and thus the LVTT offsets become out-of-sync with the LVT, resulting in verification error.

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8064554 BCEL still corrupts generic methods if bytecode offsets are modified

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8064590 BCEL still corrupts generic methods if bytecode offsets are modified

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8064592 BCEL still corrupts generic methods if bytecode offsets are modified

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8065473 BCEL still corrupts generic methods if bytecode offsets are modified

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8071108 BCEL still corrupts generic methods if bytecode offsets are modified

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8072244 BCEL still corrupts generic methods if bytecode offsets are modified

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8083928 BCEL still corrupts generic methods if bytecode offsets are modified

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8064555 BCEL still corrupts generic methods if bytecode offsets are modified

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8064557 BCEL still corrupts generic methods if bytecode offsets are modified

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8064558 BCEL still corrupts generic methods if bytecode offsets are modified

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JDK-8062608 BCEL corrupts debug data of methods that use generics

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Activity

              People

                dbuck David Buck
                dbuck David Buck
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: