[jira] [Updated] (NETBEANS-3580) Expression Lambdas cannot be debugged
[
https://issues.apache.org/jira/browse/NETBEANS-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated NETBEANS-3580:
-
Labels: debug lambda pull-request-available (was: debug lambda)
> Expression Lambdas cannot be debugged
> -
>
> Key: NETBEANS-3580
> URL: https://issues.apache.org/jira/browse/NETBEANS-3580
> Project: NetBeans
> Issue Type: Improvement
> Components: debugger - Java
>Affects Versions: 11.2, 11.3
>Reporter: Jan Lahoda
>Assignee: Akhilesh Singh
>Priority: Critical
> Labels: debug, lambda, pull-request-available
>
> Consider this source code:
> {{package org.netbeans.modules.learning.lambda.code.completion;}}
> {{import java.util.Arrays;}}
> {{public class NewClass {}}
> {{ public static void main(String... args) {}}
> {{ Arrays.stream(new String[] \{"a", "", "b"})}}
> {{ .filter(s -> !s.isEmpty()) //breakpoint here}}
> {{ .forEach(System.err::println);}}
> \{{ }}}
> {{}}}
>
> Add a breakpoint at the marked line, and run the code under the debugger. The
> debugger will stop on the breakpoint for the "filter" method invocation (OK),
> but it will not stop there for the lambda invocation (bad). So with a code
> like this, one does not see the lambda parameters, cannot step inside, etc.
> Workaround is to place the expression on a new line:
> {\{ .filter(s -> }}
> \{{ !s.isEmpty()) //breakpoint here}}
> But that requires a change to the code just for debugging - and that defies
> the purpose of debugging (which is to inspect the code *without* changes).
> The IDE is a fully updated Apache NetBeans 11.2, with nb-javac installed
> running on JDK 13:
> Product Version: Apache NetBeans IDE 11.2
> Java: 13.0.1; OpenJDK 64-Bit Server VM 13.0.1+9
> Runtime: OpenJDK Runtime Environment 13.0.1+9
> System: Linux version 4.15.0-72-generic running on amd64; UTF-8; en_US (nb)
> User directory: /tmp/nbuser.lambda.test
> Cache directory: /tmp/nbuser.lambda.test/var/cache
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3580) Expression Lambdas cannot be debugged
[
https://issues.apache.org/jira/browse/NETBEANS-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Netbeans User 2019 updated NETBEANS-3580:
-
Issue Type: Improvement (was: Bug)
> Expression Lambdas cannot be debugged
> -
>
> Key: NETBEANS-3580
> URL: https://issues.apache.org/jira/browse/NETBEANS-3580
> Project: NetBeans
> Issue Type: Improvement
> Components: debugger - Java
>Affects Versions: 11.2, 11.3
>Reporter: Jan Lahoda
>Assignee: Akshay Gupta
>Priority: Critical
> Labels: debug, lambda
>
> Consider this source code:
> {{package org.netbeans.modules.learning.lambda.code.completion;}}
> {{import java.util.Arrays;}}
> {{public class NewClass {}}
> {{ public static void main(String... args) {}}
> {{ Arrays.stream(new String[] \{"a", "", "b"})}}
> {{ .filter(s -> !s.isEmpty()) //breakpoint here}}
> {{ .forEach(System.err::println);}}
> \{{ }}}
> {{}}}
>
> Add a breakpoint at the marked line, and run the code under the debugger. The
> debugger will stop on the breakpoint for the "filter" method invocation (OK),
> but it will not stop there for the lambda invocation (bad). So with a code
> like this, one does not see the lambda parameters, cannot step inside, etc.
> Workaround is to place the expression on a new line:
> {\{ .filter(s -> }}
> \{{ !s.isEmpty()) //breakpoint here}}
> But that requires a change to the code just for debugging - and that defies
> the purpose of debugging (which is to inspect the code *without* changes).
> The IDE is a fully updated Apache NetBeans 11.2, with nb-javac installed
> running on JDK 13:
> Product Version: Apache NetBeans IDE 11.2
> Java: 13.0.1; OpenJDK 64-Bit Server VM 13.0.1+9
> Runtime: OpenJDK Runtime Environment 13.0.1+9
> System: Linux version 4.15.0-72-generic running on amd64; UTF-8; en_US (nb)
> User directory: /tmp/nbuser.lambda.test
> Cache directory: /tmp/nbuser.lambda.test/var/cache
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3580) Expression Lambdas cannot be debugged
[
https://issues.apache.org/jira/browse/NETBEANS-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Netbeans User 2019 updated NETBEANS-3580:
-
Labels: debug lambda (was: )
> Expression Lambdas cannot be debugged
> -
>
> Key: NETBEANS-3580
> URL: https://issues.apache.org/jira/browse/NETBEANS-3580
> Project: NetBeans
> Issue Type: Bug
> Components: debugger - Java
>Affects Versions: 11.2, 11.3
>Reporter: Jan Lahoda
>Assignee: Akshay Gupta
>Priority: Critical
> Labels: debug, lambda
>
> Consider this source code:
> {{package org.netbeans.modules.learning.lambda.code.completion;}}
> {{import java.util.Arrays;}}
> {{public class NewClass {}}
> {{ public static void main(String... args) {}}
> {{ Arrays.stream(new String[] \{"a", "", "b"})}}
> {{ .filter(s -> !s.isEmpty()) //breakpoint here}}
> {{ .forEach(System.err::println);}}
> \{{ }}}
> {{}}}
>
> Add a breakpoint at the marked line, and run the code under the debugger. The
> debugger will stop on the breakpoint for the "filter" method invocation (OK),
> but it will not stop there for the lambda invocation (bad). So with a code
> like this, one does not see the lambda parameters, cannot step inside, etc.
> Workaround is to place the expression on a new line:
> {\{ .filter(s -> }}
> \{{ !s.isEmpty()) //breakpoint here}}
> But that requires a change to the code just for debugging - and that defies
> the purpose of debugging (which is to inspect the code *without* changes).
> The IDE is a fully updated Apache NetBeans 11.2, with nb-javac installed
> running on JDK 13:
> Product Version: Apache NetBeans IDE 11.2
> Java: 13.0.1; OpenJDK 64-Bit Server VM 13.0.1+9
> Runtime: OpenJDK Runtime Environment 13.0.1+9
> System: Linux version 4.15.0-72-generic running on amd64; UTF-8; en_US (nb)
> User directory: /tmp/nbuser.lambda.test
> Cache directory: /tmp/nbuser.lambda.test/var/cache
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3580) Expression Lambdas cannot be debugged
[
https://issues.apache.org/jira/browse/NETBEANS-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Netbeans User 2019 updated NETBEANS-3580:
-
Affects Version/s: 11.3
> Expression Lambdas cannot be debugged
> -
>
> Key: NETBEANS-3580
> URL: https://issues.apache.org/jira/browse/NETBEANS-3580
> Project: NetBeans
> Issue Type: Bug
> Components: debugger - Java
>Affects Versions: 11.2, 11.3
>Reporter: Jan Lahoda
>Assignee: Akshay Gupta
>Priority: Critical
>
> Consider this source code:
> {{package org.netbeans.modules.learning.lambda.code.completion;}}
> {{import java.util.Arrays;}}
> {{public class NewClass {}}
> {{ public static void main(String... args) {}}
> {{ Arrays.stream(new String[] \{"a", "", "b"})}}
> {{ .filter(s -> !s.isEmpty()) //breakpoint here}}
> {{ .forEach(System.err::println);}}
> \{{ }}}
> {{}}}
>
> Add a breakpoint at the marked line, and run the code under the debugger. The
> debugger will stop on the breakpoint for the "filter" method invocation (OK),
> but it will not stop there for the lambda invocation (bad). So with a code
> like this, one does not see the lambda parameters, cannot step inside, etc.
> Workaround is to place the expression on a new line:
> {\{ .filter(s -> }}
> \{{ !s.isEmpty()) //breakpoint here}}
> But that requires a change to the code just for debugging - and that defies
> the purpose of debugging (which is to inspect the code *without* changes).
> The IDE is a fully updated Apache NetBeans 11.2, with nb-javac installed
> running on JDK 13:
> Product Version: Apache NetBeans IDE 11.2
> Java: 13.0.1; OpenJDK 64-Bit Server VM 13.0.1+9
> Runtime: OpenJDK Runtime Environment 13.0.1+9
> System: Linux version 4.15.0-72-generic running on amd64; UTF-8; en_US (nb)
> User directory: /tmp/nbuser.lambda.test
> Cache directory: /tmp/nbuser.lambda.test/var/cache
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3580) Expression Lambdas cannot be debugged
[
https://issues.apache.org/jira/browse/NETBEANS-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Lahoda updated NETBEANS-3580:
-
Description:
Consider this source code:
{{package org.netbeans.modules.learning.lambda.code.completion;}}
{{import java.util.Arrays;}}
{{public class NewClass {}}
{{ public static void main(String... args) {}}
{{ Arrays.stream(new String[] \{"a", "", "b"})}}
{{ .filter(s -> !s.isEmpty()) //breakpoint here}}
{{ .forEach(System.err::println);}}
\{{ }}}
{{}}}
Add a breakpoint at the marked line, and run the code under the debugger. The
debugger will stop on the breakpoint for the "filter" method invocation (OK),
but it will not stop there for the lambda invocation (bad). So with a code like
this, one does not see the lambda parameters, cannot step inside, etc.
Workaround is to place the expression on a new line:
{\{ .filter(s -> }}
\{{ !s.isEmpty()) //breakpoint here}}
But that requires a change to the code just for debugging - and that defies the
purpose of debugging (which is to inspect the code *without* changes).
The IDE is a fully updated Apache NetBeans 11.2, with nb-javac installed
running on JDK 13:
Product Version: Apache NetBeans IDE 11.2
Java: 13.0.1; OpenJDK 64-Bit Server VM 13.0.1+9
Runtime: OpenJDK Runtime Environment 13.0.1+9
System: Linux version 4.15.0-72-generic running on amd64; UTF-8; en_US (nb)
User directory: /tmp/nbuser.lambda.test
Cache directory: /tmp/nbuser.lambda.test/var/cache
was:
Consider this source code:
{{package org.netbeans.modules.learning.lambda.code.completion;}}
{{import java.util.Arrays;}}
{{public class NewClass {}}
{{ public static void main(String... args) {}}
{{ Arrays.stream(new String[] \{"a", "", "b"})}}
{{ .filter(s -> !s.isEmpty()) //breakpoint here}}
{{ .forEach(System.err::println);}}
{{ }}}
{{}}}
Add a breakpoint at the marked line, and run the code under the debugger. The
debugger will stop on the breakpoint for the "filter" method invocation (OK),
but it will not stop there for the lambda invocation (bad). So with a code like
this, one does not see the lambda parameters, cannot step inside, etc.
Workaround is to place the expression on a new line:
{{ .filter(s -> }}
{{ !s.isEmpty()) //breakpoint here}}
But that requires a change to the code just for debugging - and that defies the
purpose of debugging (which is to inspect the code *without* changes).
> Expression Lambdas cannot be debugged
> -
>
> Key: NETBEANS-3580
> URL: https://issues.apache.org/jira/browse/NETBEANS-3580
> Project: NetBeans
> Issue Type: Bug
> Components: debugger - Java
>Affects Versions: 11.2
>Reporter: Jan Lahoda
>Priority: Critical
>
> Consider this source code:
> {{package org.netbeans.modules.learning.lambda.code.completion;}}
> {{import java.util.Arrays;}}
> {{public class NewClass {}}
> {{ public static void main(String... args) {}}
> {{ Arrays.stream(new String[] \{"a", "", "b"})}}
> {{ .filter(s -> !s.isEmpty()) //breakpoint here}}
> {{ .forEach(System.err::println);}}
> \{{ }}}
> {{}}}
>
> Add a breakpoint at the marked line, and run the code under the debugger. The
> debugger will stop on the breakpoint for the "filter" method invocation (OK),
> but it will not stop there for the lambda invocation (bad). So with a code
> like this, one does not see the lambda parameters, cannot step inside, etc.
> Workaround is to place the expression on a new line:
> {\{ .filter(s -> }}
> \{{ !s.isEmpty()) //breakpoint here}}
> But that requires a change to the code just for debugging - and that defies
> the purpose of debugging (which is to inspect the code *without* changes).
> The IDE is a fully updated Apache NetBeans 11.2, with nb-javac installed
> running on JDK 13:
> Product Version: Apache NetBeans IDE 11.2
> Java: 13.0.1; OpenJDK 64-Bit Server VM 13.0.1+9
> Runtime: OpenJDK Runtime Environment 13.0.1+9
> System: Linux version 4.15.0-72-generic running on amd64; UTF-8; en_US (nb)
> User directory: /tmp/nbuser.lambda.test
> Cache directory: /tmp/nbuser.lambda.test/var/cache
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
