Opened 6 years ago
Closed 6 years ago
#14321 closed bug (fixed)
Debugger says "Source file unavailable" for structs/classes declared in method bodies
| Reported by: | waddlesplash | Owned by: | anevilyak |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Applications/Debugger | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Ran into this one while attempting to debug a PackageKit problem.
Test file attached. As you can see, it triggers Debugger inside an operator() inside a struct that is declared within a function, the same way this is sometimes done in PackageKit.
When compiled with -g, run, and then attaching Debugger after the crash dialog shows, and then selecting the method call above the debugger call, only disassembly is shown with "Source file unavailable." If you go one up the call stack into main(), then source is displayed just fine.
hrev52135, gcc2h.
Attachments (1)
Change History (4)
by , 6 years ago
comment:1 by , 6 years ago
comment:2 by , 6 years ago
Same issue with GCC7, indeed. The function's mangled name shows up properly in the callstack, though.
Note:
See TracTickets
for help on using tickets.
Would be interesting to know if the same issue is seen with gcc7 or not. It'll be a while before I can look into it in any case, owing to some technical problems.