Opened 13 years ago
Closed 13 years ago
#8095 closed bug (fixed)
Source file path resolution doesn't work as is should
| Reported by: | bonefish | Owned by: | anevilyak |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications/Debugger | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
hrev43130, gcc 2, Haiku image cross-built on Linux
The intelligent source file path resolution doesn't work as expected. After specifying the path to the first source file, the paths for other source files should be guessed automatically, if their location relative to the first source file has not changed (i.e. is the same as when compiled).
Tested debugging DebugAnalyzer, source copied to the image via the AddSourceDirectoryToHaikuImage rule. The DebugAnalyzer.cpp source file was specified after starting Debugger before running the program. A later crash in model_loader/ModelLoader.cpp did not show the source file and the file had to be specified manually as well.
Change History (7)
comment:1 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 13 years ago
comment:4 by , 13 years ago
| Status: | in-progress → assigned |
|---|
Problem found: LocatableDirectory::AddEntry() is never actually called, thus when FileManager::_LocateEntries() tries to traverse and update every similar file, the directories have no entries to update and the function returns immediately without doing anything. At the moment I'm not yet certain as to the correct place to add that call though, and I'm out of time for tonight.
If you remember more clearly and can easily fix it, feel free, otherwise I'll try to grok the structure of the file manager a bit better sometime this week so I can fix it myself.
comment:5 by , 13 years ago
I can't say I recall the details of the file manager code. You're probably already at least as familiar with the code as I am. Although a bit annoying (particularly since the file dialog doesn't remember its directory) it isn't high priority either.
comment:6 by , 13 years ago
| Status: | assigned → in-progress |
|---|
comment:7 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | in-progress → closed |
Intelligent location fixed, and file panel modified to remember its last location in hrev43263.
Will dig into this, since I had to make changes to the source file resolution code to get it to work at all when I exposed that functionality via the UI, it's possible I broke some aspect of it. Out of curiosity, were the source paths in the DWARF info absolute or relative with the binary you had?