This bug
  4920751 Need both JNI signatures and Generic signatures in the Local Variable Table

states that generic signatures have to be added to the Local Variable Table
in the .class file. This will be done in a backward comptible way so that
existing Hotspot code can still read the current form of Local Variable Table.
The new generic signatures have to be extracted from the new part
of the Local Variable Table, saved in Hotspot data structures, and
output in the JVMTI GetLocalVariableTable function.
Modified by :
###@###.### 2003-09-19

The most recent Spec says:

 "4.8.12 The LocalVariableTypeTable Attribute

 The LocalVariableTypeTable attribute is an optional variable-length
 attribute of a Code (§4.8.3) attribute. It may be used by debuggers
 o determine the value of a given local variable during the execution
 of a method. If LocalVariableTypeTable attributes are present in the
 attributes table of a given Code attribute, then they may appear in
 any order. There may be no more than one LocalVariableTypeTable
 attribute per local variable in the Code attribute.

 The LocalVariableTypeTable attribute differs from the
 LocalVariableTable attribute in that it provides signature
 information rather than descriptor information. This difference is
 only significant for variables whose type is a generic reference type.
 Such variables will appear in both tables, while variables of other
 types will appear only in LocalVariableTable."

It means that the Local Variable Table is always a source of JNI signatures.
Generic signatures should be taken from the Local Variable Type Table
if it does exist and from the Local Variable Table otherwise.

Modified by :
###@###.### 2003-12-02

Name: pvR10198 Date: 12/12/2003


This bug affects the following test from testbase_nsk:

    nsk/jvmti/GetLocalVariableTable/localtab005

Pavel Vysotski <###@###.###>

======================================================================