[
https://issues.apache.org/jira/browse/GROOVY-9610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Primo Modica updated GROOVY-9610:
---------------------------------
Affects Version/s: 2.4.16
> Unreachable line numbers after ARETURN in bytecode
> --------------------------------------------------
>
> Key: GROOVY-9610
> URL: https://issues.apache.org/jira/browse/GROOVY-9610
> Project: Groovy
> Issue Type: Bug
> Components: bytecode
> Affects Versions: 2.4.16, 2.4.17
> Reporter: Primo Modica
> Priority: Major
> Labels: bytecode, jacoco
>
> This ticket is the same of GROOVY-9126 but for a different groovy version.
> From the above ticket:
> {noformat}
> Starting with Groovy 2.5.5, unreachable line numbers were added to the byte
> code. This causes tools like JaCoCo
> to report uncovered lines. Removing these line numbers after the ARETURN
> would be helpful.
> https://github.com/jacoco/jacoco/issues/884
> ARETURN
> L1
> LINENUMBER 16 L1 <-- new line number that cant be hit after ARETURN
> FRAME FULL [] [java/lang/Throwable]
> NOP
> ATHROW
> LOCALVARIABLE this Lcom/company/Form; L0 L1 0
> MAXSTACK = 2
> MAXLOCALS = 1
> {noformat}
> The problem is that the bug has been introduced in GROOVY-7647 that belongs
> to the changelog of 2.4.16
> ([http://groovy-lang.org/changelogs/changelog-2.4.16.html])
> Request:
> Please fix also versions >= 2.4.X
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
