> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/education/faq/crash-details-active-thread.md).

# Crash details 'Active Thread'

The **Method** column contains a list of methods in the stack trace of the thread that caused your program to crash. Depending on the [platform](/integrations/integrations.md) you may see methods that don't match your source code. This is because platforms such as [Windows Native](/integrations/desktop/cplusplus.md), [.NET](/integrations/desktop/bugsplat-for-dot-net.md), [Crashpad](/integrations/desktop/crashpad.md), [Breakpad](/integrations/desktop/breakpad.md), [macOS](/integrations/desktop/macos.md), [Unity](/integrations/game-development/unity.md), and [Unreal](/integrations/game-development/unreal-engine.md) require you to upload [symbols](/guides/working-with-symbol-files.md) for each version you release in order to calculate the correct method names. For more information on how to upload symbols please see the documentation for your [platform](/integrations/integrations.md).

![Crash Details ACtive Thread](https://976110677-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LBMgmIcgkIXSUfnXDSv%2Fsync%2F7fbeb1232dce2f990ade1b02933d7de26e4a51a1.png?generation=1631220494948153\&alt=media)

Clicking the **>** (greater than symbol) in the left-most column will expand the **Row Details** view.

The **Row Details** view will display **Group Rules**, **Ignore Function**, and **Ignore File** buttons that will take you to the grouping rules screen where you can create a [Group](/guides/grouping-crashes.md). Grouping at a different level of the call stack is useful in cases such as a crash that occurs in a 3rd party library, or when additional stack frames are added by a crash reporter.

Additionally, for [Windows Native](/integrations/desktop/cplusplus.md) crashes the **Row Details** view will show a table of [Local Variables and Function Arguments](https://blog.bugsplat.com/local-variables-function-arguments/).

When you land on the crash details page, BugSplat starts a debugging session in the background that will calculate additional information about the crash. This additional information includes the call stacks for the non-active threads, register values, loaded modules, and function argument and local variable values. You will see a loading indicator when this information isn't yet available.


---

# 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.bugsplat.com/education/faq/crash-details-active-thread.md?ask=<question>&goal=<user_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.