You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Eric Milles (Jira)" <ji...@apache.org> on 2020/01/22 19:59:00 UTC

[jira] [Updated] (GROOVY-9373) ASM: rework line numbers for blocks with fast-path or return statement insertion

     [ https://issues.apache.org/jira/browse/GROOVY-9373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Milles updated GROOVY-9373:
--------------------------------
    Description: 
GROOVY-4063, GROOVY-7647, GROOVY-8742, GROOVY-9076, GROOVY-9199 and GROOVY- present (possibly) conflicting concerns.  Code coverage metrics are thrown off when line number information exists outside of the reachable paths in the bytecode.  Debug break and step exhibit strange behaviors when the bytecode contains insufficient or duplicated line number information.

Can the ASM changes in StatementWriter be reworked to address these concerns?

  was:
GROOVY-4063, GROOVY-7647, GROOVY-8742, GROOVY-9076, GROOVY-9199 and GROOVY-9209 present (possibly) conflicting concerns.  Code coverage metrics are thrown off when line number information exists outside of the reachable paths in the bytecode.  Debug break and step exhibit strange behaviors when the bytecode contains insufficient or duplicated line number information.

Can the ASM changes in StatementWriter be reworked to address these concerns?


> ASM: rework line numbers for blocks with fast-path or return statement insertion
> --------------------------------------------------------------------------------
>
>                 Key: GROOVY-9373
>                 URL: https://issues.apache.org/jira/browse/GROOVY-9373
>             Project: Groovy
>          Issue Type: Bug
>    Affects Versions: 2.4.18, 2.5.9, 3.0.0-rc-3
>            Reporter: Eric Milles
>            Assignee: Eric Milles
>            Priority: Major
>
> GROOVY-4063, GROOVY-7647, GROOVY-8742, GROOVY-9076, GROOVY-9199 and GROOVY- present (possibly) conflicting concerns.  Code coverage metrics are thrown off when line number information exists outside of the reachable paths in the bytecode.  Debug break and step exhibit strange behaviors when the bytecode contains insufficient or duplicated line number information.
> Can the ASM changes in StatementWriter be reworked to address these concerns?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)