Closed Bug 292751 Opened 20 years ago Closed 19 years ago

LXR-generated link to included header files returns a message "This file does not exist."

Categories

(Webtools Graveyard :: MXR, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 82510

People

(Reporter: eh-bugzilla, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 Build Identifier: A number of header files are apparently not being indexed. nsIWidget.h, nsISupports.h, nsIEventListener.h, nsIMouseListener.h. I've been trying to track down exactly how Firefox processes events in order to track down an automation problem. I'm stuck at this point because I can't see the sources and it's not worth my time to set it all up locally. Reproducible: Always Steps to Reproduce: 1. Browse to http://lxr.mozilla.org/seamonkey/source/widget/src/xpwidgets/nsBaseWidget.h#41 2. Click on link to nsIWidget.h Actual Results: Observed "This file does not exist" message Expected Results: Presented HTML generated from the source file "nsIWidget.h"
no, it does index them. but I believe that the links LXR generates for these files always just look in the same directory as the file, and those files live elsewhere.
(In reply to comment #1) > no, it does index them. but I believe that the links LXR generates for these > files always just look in the same directory as the file, and those files live > elsewhere. It may indeed index them, but the link is still broken. Doesn't LXR incorporate a search-path to generate its file links?
I don't have time to work on this right now. Open for somebody else to take a whack at it.
Assignee: chase → nobody
this is fixed on mxr-test.
Whiteboard: DUPEME
*** This bug has been marked as a duplicate of 82510 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
QA Contact: timeless → lxr
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.