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.
If I start my debug session by Run->Step Into then only the Pause and Finish buttons are enabled. The call stack shows the correct line (well, it shows the main function line) but there is no PC annotation in the editor. This works OK on Solaris (I didn't try Linux).
I cannot reproduce the problem on my Windows system. All buttons are enabled, except of "Run to Cursor" and "Apply Code Changes" (which is correct, because they are not supported yet). All other buttons are enabled and work properly. Is there something special in the project you debug? Perhaps there are some exceptions in the log file?
I just tried it 3 more times. The 1st time my nb had been running for awhile and I'd started/stopped many sessions. That time it did the buttons correctly (and the PC annotation also). After I killed my nb and restarted, I was back to the buttons not getting updated after a step into.
Please, provide more details (OS, gdb version, log file from Debugger Console) and check out the log file - perhaps there are some exceptions or error messages.
I think I understand what can cause such a strange problem (step buttons are disabled). I suppose "Continue" button is also disabled, correct? My guess is: debugger did not start the program. I think "Debugger Console" shows "Status: Loaded", which means that IDE did not send "-exec-run" command to gdb. Please, provide the complete log from "Debugger Console" window, and I will explain why it happened. I suppose the root of the problem is in breakpoints, which means IZ 84553 (Start Debugging is broken) is not completely fixed.
Fixed for several known cases: case 1: On Unix if an application doesn't know where all of its required shared libraries are then a SIGKILL is sent and the process terminates. We didn't handle this case and the buttons looked like the process was running. case 2: If gdb never responded then we were left with no buttons except Finish enabled. While the user could press the Finish button and end the session, there was no UI feedback on what was happening. Now a message is posted after 30 seconds telling the user that gdb never responded. This is most likely to happen on Windows where the gdb being used doesn't correspond to the compilers used to compile the app.
> Fixed for several known cases I should have said "Fixed all known cases". There is a potential for other problems to cause this behavior because but this handles the 2 cases I've seen.