Closed Bug 1197839 Opened 10 years ago Closed 5 years ago

Definition sites of macros defined by functions not found

Categories

(Webtools Graveyard :: DXR, defect)

defect
Not set
normal

Tracking

(firefox43 affected)

RESOLVED WONTFIX
Tracking Status
firefox43 --- affected

People

(Reporter: erik, Unassigned)

Details

(split off from 1196917) 1. Go to DXR. 2. Search for RegisterNonJSSizeOfTab. 3. Observe three hits: - 1 call; - 1 declaration in an idl file; - 1 declaration in the generated header from the idl file. 4. Click on the result with the file featuring the call, nsWindowMemoryReporter.cpp. 5. Click on "RegisterNonJSSizeOfTab", select "jump to definition". This takes me to the declaration (in a generated .h) rather than any definition. Nathan would like to be sent to the defining macro at xpcom/base/nsMemoryReporterManager.cpp#2423.
Nathan, that's quite a tangled web of macro calls. What made you choose GET_MEMORY_REPORTER_MANAGER as the defining macro rather than, say, DEFINE_REGISTER_SIZE_OF_TAB?
Flags: needinfo?(nfroyd)
(In reply to Erik Rose [:erik][:erikrose] from comment #1) > Nathan, that's quite a tangled web of macro calls. What made you choose > GET_MEMORY_REPORTER_MANAGER as the defining macro rather than, say, > DEFINE_REGISTER_SIZE_OF_TAB? Um, I thought I did pick DEFINE_REGISTER_SIZE_OF_TAB as the defining macro! nsMemoryReporterManager.cpp, line 2423 reads (at least in my local copy): DEFINE_REGISTER_SIZE_OF_TAB(NonJS); Ah, but I see things have changed since I made that request! MXR currently lists the above line as line 2477. Whatever line in nsMemoryReporterManager.cpp the above text appears on, that's the line I want to be taken to. :)
Flags: needinfo?(nfroyd)
Aha, the universe makes sense again! Thanks! :-)

DXR is no longer available. Searchfox is now replacing it.
See meta bug 1669906 & https://groups.google.com/g/mozilla.dev.platform/c/jDRjrq3l-CY for more details.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.