![]() I would expect to be informed that the frame is without debugging symbols and possibly draw a button to show dissassembly now hit a series of "Step over" so that the debugger would reach one of the intermediary frames which don't debugging symbols. hit "Continue" Now it should reach the second breakpoint start a debugging session It should stop at the first breakpoint insert another breakpoint so that when is hit it falls behind the first one but there are some intermediary frames which don't have debugging symbols ![]() insert one breakpoint so that the all bt frames has debugging symbols up to it I addition there seem to be a Java exception in: In some scenarios, complex C++ with templates render gdb to issue a SIGINT to the debugged process, hanging the gui and display repeating various error messages when hitting "Terminate" icon. System: Linux version 4.4.0-81-generic running on amd64 UTF-8 en_US (nb) Runtime: Java(TM) SE Runtime Environment 1.8.0_131-b11 Updates: NetBeans IDE is updated to version NetBeans 8.2 Patch 2 A gdb debug session which triggers the behavior
0 Comments
Leave a Reply. |