> 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/kclocatesymbol.md).
# KCLocateSymbol
## Description
Search the kernelcache for a symbol by name, across the KEXTs' symbol tables. The tables are read from the cache file, so a KEXT nobody has loaded is searched like any other.
Choosing the action opens a small **query prompt**: enter a substring — the field keeps a history of past queries — and confirm.
Available from the KC Index context menu, under **Locate**.
The "Locate > Symbol" entry in the KC Index context menu
The query prompt, with the Options group expanded
Behind the **Options** group (collapsed by default):
* **Ignore case** — match the needle whatever its case.
* **Search linked collections** — also search the collection this one links to, which on a macOS System KC is its Boot KC.
Confirming runs the search and opens the **KC symbols** panel with the matches. The panel keeps the same query field and Options, so you can refine in place — edit the text and press Enter, or click the **Search** button.
{% hint style="info" %}
A modern iOS kernelcache carries no symbol table at all, so no spelling of the needle can match. The prompt says so rather than leave you to read an empty result as a missing symbol.
{% endhint %}
On a cache with no symbols, the prompt says why nothing can match
### Result tree
Hits are grouped by the KEXT that owns them, and under it by the section they sit in. Each leaf marks the part of its text that matched, and carries the address and whether its KEXT is currently loaded.
Double-clicking a leaf jumps to the hit, mapping the owning KEXT first if it is not loaded yet.
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/kclocatesymbol.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.
