[
https://issues.apache.org/jira/browse/BCEL-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated BCEL-27:
-------------------------------
Description:
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
was:
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
Priority: Major
Environment: (was: Operating System: other
Platform: Other)
Affects Version/s: (was: unspecified)
Fix Version/s: 5.2
Priority: (was: P3)
Severity: (was: enhancement)
> Verifier does not report the signature of methods not found
> -----------------------------------------------------------
>
> Key: BCEL-27
> URL: https://issues.apache.org/jira/browse/BCEL-27
> Project: Commons BCEL
> Issue Type: Improvement
> Components: Main
> Reporter: Stephen Kolaroff
> Assignee: Apache Commons Developers
> Fix For: 5.2
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.2#6252)