Community
Participate
Working Groups
Build ID: I20080523-0100 Steps To Reproduce: 1. Add "foo" method in an ANSI C project and call it from "main" 1. After build, "open" executable (binaries) in C++ Project view 2. choose "_foo" symbol and invoke "Toggle breakpoint" action. 3. Uncheck "Show source files in binaries" from "C/C++ - >Debug" workspace preferences. 3. Start debug. 4. In breakpoint view, the "_foo" breakpoint is listed but does not have the resolved tickmark. 5. When resuming application, breakpoint will never be hit More information: Same issue is when setting breakpoint from "Modules" view.
Created attachment 104126 [details] CBreakpointManager patch ICDIFunctionBreakpoints on function elements from binary objects do not have a source handle. Consider this case in CBreakpointManager#isTargetBreakpoint. See attached patch
If it creates ICFunctionBreakpoint we should check for this type not for source handle.
Created attachment 104164 [details] CBreakpointManager patch with checking for ICFunctionBreakpoint added The code that makes decision if to use source matching for breakpoints was refactored into a separate method "breakpointUsesSourceMatching".
I'll take it to apply patch
-> patch applied on head, thanks. Breakpoints still won't work if project uses Absolute File Path source lookup but this is different bug
(In reply to comment #5) > -> patch applied on head, thanks. The patch introduces a potential NPE, namely when breakpoint.getSourceHandle() returns null.
Created attachment 104435 [details] Fix potential NPE Patch to HEAD that fixes the NPE.
Thanks Anton for noticing, I will apply the fix (it was working though for some reason when I tested it, I guess because it returned "")