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

Make sure {type,obj}ArrayOopDesc accessors check the bounds

XMLWordPrintable

    • b09

        I was debugging some new VM patch, and figured it was a memory stomp due to wrong index passed to objArrayOopDesc::obj_at_put. That method does not assert the index at all, which hides the errors and silently corrupts the heap, until something else discovers it. Some objArrayOopDesc accessors do verify the index against the bounds.

        Same thing goes for typeArrayOopDesc.

              shade Aleksey Shipilev
              shade Aleksey Shipilev
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: