Missing stack frame titles

[sindresorhus]

Platform

macOS

Environment

Production

Installed

Swift Package Manager

Version

8.38.0

Xcode Version

16.0

Did it work on previous versions?

No response

Steps to Reproduce

Many stack trace frames show a ? instead of a symbol reference.

Example:

Expected Result

I expected the stack frame to show the method/property at that location.

Actual Result

Stack trace: https://sindresorhus.sentry.io/share/issue/784ced2af05b481d864831afb7c66548/

Are you willing to submit a PR?

No response

[philipphofmann]

This looks more like a problem with symbolication. I'm going to transfer this issue to the main repo. This could be related to getsentry/symbolic#873.

[getsantry]

Routing to @getsentry/product-owners-issues-source-maps for triage ⏲️

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[jangjodi]

It looks like our symbolication logic is handled by @getsentry/product-owners-processing , so I will transfer it there

[getsantry]

Routing to @getsentry/product-owners-processing for triage ⏲️

[loewenheim]

Hi, thank you for the report. We'll investigate as soon as possible.

[jjbayer]

@sindresorhus sorry for the long wait. We are investigating whether the question marks show up because the function names in question are actually missing for the dSYM that you uploaded, or if there is a bug in getsentry/symbolic that prevents us from showing the correct name. Would you be able to share with us one of the function names that you expect to show instead of ?? That will help us look for the function in the dSYM file. Thanks!

[sindresorhus]

+0x1cd155 ? (AX.swift:982)

Points to:

try value(for: attribute, as: [AXUIElement].self)?.map { T($0) } ?? []

in:

extension AX.Element {
	func elements<T: AX.Element>(
		for attribute: NSAccessibility.Attribute,
		as type: T.Type
	) throws(AXError) -> [T] {
		try value(for: attribute, as: [AXUIElement].self)?.map { T($0) } ?? []
	}
}

[loewenheim]

In the DWARF we can see the name init (of type Supercharge::Window) for this code location. The link from the inlined function to the original entry contains an indirection via a DW_AT_specification entry. It's possible that we aren't following this indirection correctly and can't resolve the name for this reason.

[jjbayer]

Thanks @loewenheim, I will see if I can figure out where exactly in code this fails and if it can be fixed.

[loewenheim]

Wrote up everything we have so far https://www.notion.so/sentry/Missing-DWARF-function-names-1528b10e4b5d80ee9962e337c64a2b0c