This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 256133 - [mixeddev] Debugger view shows incorrect threads
Summary: [mixeddev] Debugger view shows incorrect threads
Status: RESOLVED DUPLICATE of bug 255990
Alias: None
Product: cnd
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 8.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: henk89
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-23 11:32 UTC by Vladimir Kvashin
Modified: 2015-12-21 10:46 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
gdb log (118.38 KB, text/x-log)
2015-10-23 11:32 UTC, Vladimir Kvashin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Kvashin 2015-10-23 11:32:31 UTC
Created attachment 156935 [details]
gdb log

I have a very simple java program with JNI:
(native part is trivial, just generated it and added "return 123";)

public class JavaApplication3 {
    private native int caclculate();    
    public static void main(String[] args) {        
        System.loadLibrary("CppJNILibrary_3");        
        int res = new JavaApplication3().caclculate(); // step into
        System.out.println("res = " + res);
    }    
}

When I step into JavaApplication3().caclculate(), debugging view shows 27 threads - which is correct (at least "info threads" gives me the same amount).

But when I expand each thread, it shows the same stack:
Java_javaapplication3_JavaApplication3_caclculate (env=0x7fa5d0013000, object=0x8)
?? ()
?? ()
?? ()
?? ()
?? ()
?? ()
?? ()
?? ()
Comment 1 Vladimir Kvashin 2015-10-23 11:33:40 UTC
When I make other thread current (via gdb command in console or via "threads" window), then this new thread stack is shown in all threads
Comment 2 Vladimir Kvashin 2015-10-23 11:55:48 UTC
The same happens in the version built on release81 from enum.
Comment 3 henk89 2015-12-14 12:10:29 UTC

*** This bug has been marked as a duplicate of bug 255990 ***