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.
Several times stepping from Java into native went ok, but disassembly window became focused. When I switched focus to appropriate .cpp file, I saw green breakpoint line there, and everythink worked ok. Frankly that was probably Studio specific.
Created attachment 156783 [details] This have just repeated. Here is gdb log But it seems to be rather an issue of synchronization somewhere in NB
Created attachment 156785 [details] One more case when it stays in disassembly. One more case when it stays in disassembly. And yes, it is a pure NetBeans problem - today I'm running NetBeans, not Studio. Again, as soon as I manually switched to .cpp, everything works fine.
I think you speak about CR 20513293. Every day 5-10 automatic tests fails because Disassembly tab appears. Easy reproduce via NetBeans and Attach window.
The root cause of the issue is the sync problem in NativeDebuggerImpl.updateLocation(): the outcome depends on the order of the execution of SwingUtilities.invokeLater. Sometimes file operations inside run() change the execution order that results in showing outdated location (including disassembled code)
Created attachment 159203 [details] The patch makes current location more accurate
Created attachment 159212 [details] The patch makes current location more accurate
Created attachment 159254 [details] proposed patch
Fixed in: http://hg.netbeans.org/cnd-main/rev/5e5963338e48
Integrated into 'main-silver', will be available in build *201604150001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/5e5963338e48 User: Nikolay Koldunov <henk89@netbeans.org> Log: Fixed #255996 - [mixeddev] stepping from Java into native sometimes stays in disassembly
verified in builds on enum server
The issue is not fixed yet in patch from staging UC.
It looks like opening the java source file in the editor before starting debugger makes difference.
*** Bug 258180 has been marked as a duplicate of this bug. ***