Opened 14 years ago
Closed 14 years ago
#6974 closed bug (fixed)
Stepping into functions in Debugger shows extra blank source
| Reported by: | stippi | Owned by: | anevilyak |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications/Debugger | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
This is a GCC4 based hybrid build of hrev39815, but I think I've seen this before. I've made a debug build of MediaPlayer and launched it in Debugger via the command line. I've inserted a breakpoint at a random location in the startup code. Whenever I step into a function, no matter if it's within the same source file or another file, there will first be a blank source code view, and the stack strace showing a weird entry at the top with the path to the MediaPlayer executable instead of a function. Pressing the Step Over button again makes Debugger arrive at the correct location in the flow of code. In another words, you have to press the Step Into button twice, and the intermediate state is weird.
Change History (4)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → in-progress |
comment:4 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | in-progress → closed |
Note:
See TracTickets
for help on using tickets.
Currently that's more or less expected since the PLT isn't yet accounted for. Since the weak symbols changes, the PLT is involved in every call, hence what you're seeing (the blank source is the intermediate step into the linkage table ).