![]() ![]() But when to query ?ġ) Each time the debugged program is stopped ? that would cause performance problem when there are many breakpoints in the Eclipse workspace.Ģ) Set gdb to stop on shared library loading and query at that time ? that would cause the bug described in this Volodya's blog That means DSF has to query gdb for the breakpoint status. But unfortunately gdb does not send any notification when a pending breakpoint is resolved. The best solution to the issue is to let Eclipse/DSF treat a pending breakpoint (we can know if a breakpoint is pending from GDB reply to "break-insert -f" command) as uninstalled, and only mark it as installed when it is resolved by gdb. And all those breakpoints GDB cannot resolve will be set as pending breakpoints in GDB, which means all breakpoints in Eclipse UI will be shown as resolved/installed (the blue breakpoint dot is checked). ![]() In DSP, we can use that MI command for setting breakpoint, which would solve the breakpoint problem with shared library.īut the major issue with the solution is: when we start debugging project A in Eclipse, Eclipse will ask GDB to set all breakpoints in the workspace including those in project A and those in other totally unrelated projects. ![]() The corresponding MI command is "break-insert -f". The pending breakpoint support is provided in gdb 6.8 and above. Updated solution to fix decrementInstallCount and including JUnit tests Updated "Suggested approach to fix" to try to make it work with the diff viewĮxample library loading project for WindowsĮxample library loading project for Windows (MinGW)įix to set all breakpoints to allow pendingīetter fix to set all breakpoints to allow pending Screen shot of Wind River's breakpoint status dialog. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |