> ## Documentation Index
> Fetch the complete documentation index at: https://docs.traceback.cc/llms.txt
> Use this file to discover all available pages before exploring further.

# Stack Traces & Symbolication

> How Traceback captures runtime call stacks and reconstructs original source code.

Stack traces are the core artifact when investigating why code failed. Traceback automatically normalizes and symbolicates stack traces across all supported languages.

## Anatomy of a Stack Frame

A processed stack frame contains:

* **File Path**: Original relative file path (e.g., `src/billing/subscription.ts`)
* **Function Name**: The calling function or closure
* **Line & Column**: Exact line and column index in source
* **Context Lines**: 5 lines of source code preceding and following the failure
* **In-App Marker**: Differentiates your application code from third-party vendor dependencies (`node_modules`)

***

## Minified vs. Symbolicated Stacks

<Tabs>
  <Tab title="Symbolicated (With Source Maps)">
    ```typescript theme={null}
    // src/controllers/checkout.ts:48:12
    export async function chargeCustomer(user: User, amount: number) {
      if (!user.stripeCustomerId) {
        throw new PaymentError("Customer has no payment method configured");
      }
      return await stripe.charges.create({ ... });
    }
    ```
  </Tab>

  <Tab title="Raw Minified Stack">
    ```text theme={null}
    Error: Customer has no payment method configured
        at t.chargeCustomer (https://cdn.example.com/assets/app.min.js:1:84712)
        at async e.processCart (https://cdn.example.com/assets/app.min.js:1:91438)
    ```
  </Tab>
</Tabs>

***

## Setting Up Automatic Symbolication

To enable automatic symbolication, upload source maps during your build:

```bash theme={null}
# Uploading via Traceback CLI
traceback sourcemaps upload --release "web@2.4.0" ./build
```

Read our [Source Maps Guide](/guides/sourcemaps-and-debug-symbols) for CI/CD integrations.