> 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/dsclocatestring.md). # DSCLocateString ## Description Search the cache's bytes for a string literal. Choosing the action opens a small **query prompt**: enter a substring — the field keeps a history of past queries — and confirm. The **Options** group, collapsed by default, controls case-insensitive matching, the search scope (per-image vs entire files) and what is scanned (code sections, `.symbols` sidecar, other adjacent files). Available from the DSC Index context menu, under **Locate**.
Locate > String

The "Locate > String" entry in the DSC Index context menu

DSC strings query prompt

The query prompt, with the Options group expanded

Confirming runs the search and opens the **DSC strings** panel with the matches. The panel keeps the same query field and Options, so you can refine the search in place — edit the text and press Enter, or click the **Search** button. ### Result tree Hits are grouped by their containing image (or file, when scoped to entire files); unlike the [DSC Index](/ida-9.5/ida-actions/opendscindex.md), this tree exposes one extra level of grouping — the **section** the literal lives in (`__cstring`, `__oslogstring`, etc.) — useful when filtering log strings out of regular ones. Each leaf shows the matched literal **in context**: not just the matched substring, but a few neighbouring bytes on either side, so the hit can be read as part of a broader literal at a glance (e.g. searching `nil completion` shows up as `%{public}@nil completion handler`). The leaf also carries its address; double-clicking jumps to the address — and triggers an on-demand load of the owning image if it isn't loaded yet.
DSC strings panel

The DSC strings search panel

See [DSC Workflow](/ida-9.5/core/disassembler/concepts/dsc-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/dsclocatestring.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.