You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Jeff Vincent (Jira)" <ji...@apache.org> on 2020/01/14 00:14:00 UTC
[jira] [Updated] (NETBEANS-3692) "Java->Java Debugger: New
breakpoints suspend: all threads" Doesn't work
[ https://issues.apache.org/jira/browse/NETBEANS-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Vincent updated NETBEANS-3692:
-----------------------------------
Description:
In trying to set conditional breakpoints to debug specific issues with TestNG test cases, I am seeing odd results where Netbeans displays odd values for variables. Thinking this was an issue with concurrency in my multi-threaded TestNG test class, I hoped to stop all running threads once a breakpoint is hit so I changed the option to suspend all threads when a new break point is hit:
!image-2020-01-13-17-01-16-941.png|width=504,height=442!
However, when a break point is hit, all the threads in the pool remain running until they too hit a break point. The interesting thing to note is that the condition specified should only be hit TWICE in the entire test run, yet multiple threads seem to hit the break point (I am going to enter this as separate issue):
!image-2020-01-13-17-05-39-566.png|width=547,height=325!
I may be missing something, but my expectation is that all threads should pause once the first break point is hit. Is this the expected behavior?
was:
In trying to set conditional breakpoints to debug specific issues with TestNG test cases, I am seeing odd results where Netbeans displays odd values for variables. Thinking this was an issue with concurrency in my multi-threaded TestNG test class, I hoped to stop all running threads once a breakpoint is hit so I changed the option to suspend all threads when a new break point is hit:
!image-2020-01-13-17-01-16-941.png|width=504,height=442!
However, when a break point is hit, all the threads in the pool remain running until they too hit a break point. The interesting thing to note is that the condition specified should only be hit TWICE in the entire test run, yet multiple threads seem to hit the break point (I am going to enter this as separate issue):
!image-2020-01-13-17-05-39-566.png|width=547,height=325!
I may be missing something, but my expectation is that all threads should pause once the first break point is hit. Is this the not the expected behavior?
> "Java->Java Debugger: New breakpoints suspend: all threads" Doesn't work
> -------------------------------------------------------------------------
>
> Key: NETBEANS-3692
> URL: https://issues.apache.org/jira/browse/NETBEANS-3692
> Project: NetBeans
> Issue Type: Bug
> Components: debugger - Java
> Affects Versions: 11.2
> Environment: Product Version: Apache NetBeans IDE 11.2
> Java: 1.8.0_221; Java HotSpot(TM) 64-Bit Server VM 25.221-b11
> Runtime: Java(TM) SE Runtime Environment 1.8.0_221-b11
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb)
> Reporter: Jeff Vincent
> Priority: Major
> Labels: debugging
> Attachments: image-2020-01-13-17-01-16-941.png, image-2020-01-13-17-05-39-566.png
>
>
> In trying to set conditional breakpoints to debug specific issues with TestNG test cases, I am seeing odd results where Netbeans displays odd values for variables. Thinking this was an issue with concurrency in my multi-threaded TestNG test class, I hoped to stop all running threads once a breakpoint is hit so I changed the option to suspend all threads when a new break point is hit:
> !image-2020-01-13-17-01-16-941.png|width=504,height=442!
> However, when a break point is hit, all the threads in the pool remain running until they too hit a break point. The interesting thing to note is that the condition specified should only be hit TWICE in the entire test run, yet multiple threads seem to hit the break point (I am going to enter this as separate issue):
> !image-2020-01-13-17-05-39-566.png|width=547,height=325!
> I may be missing something, but my expectation is that all threads should pause once the first break point is hit. Is this the expected behavior?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists