> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/ida-9.5/ida-actions/kclocateaddress.md). # KCLocateAddress ## Description Given an address, report where it lives in the kernelcache: the region that covers it, the KEXT that owns that region, and the collection the KEXT came from. Answered from the cache layout, so it works for an address in a KEXT nobody has loaded. Available from the KC Index context menu, under **Locate**.
Locate > Address

The "Locate > Address" entry in the KC Index context menu

Choosing the action asks for an address, then selects the matching region in the index, expanding whatever folders it takes to show it. This is the one to reach for with an address out of a panic log or a stack trace, before deciding what to load. See [Kernelcache Workflow](/ida-9.5/core/disassembler/concepts/kc-workflow.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hex-rays.com/ida-9.5/ida-actions/kclocateaddress.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.