DO NOT REPLY [Bug 20465] New: - Verifier does not report the signature of methods not found

[email protected]
Newsgroups gmane.comp.jakarta.bcel.devel
Message-ID <[email protected]>
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20465>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20465

Verifier does not report the signature of methods not found

           Summary: Verifier does not report the signature of methods not
                    found
           Product: BCEL
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Main
        AssignedTo: [email protected]
        ReportedBy: [email protected]


When JustICE finds that INVOKEXXX instruction references non-existing method, it
reports the method name, but not the method signature: (Pass 3a)
"constraint violated: Referenced method 'XXXX' with expected signature not found
in class 'my.package.Clazz'. The native verifier possibly allows the method to
be declared in some superclass or implemented interface, which the Java Virtual
Machine Specification, Second Edition does not."

It would be mutch better if along with the method name, its arguments and return
types (signature) is reported.

Regards, 
Cheffo
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.