Skip to content

Conversation

@LukasKastern
Copy link

This change exposes a list in the DebugSymbolsTab and SentryCliOptionsEditor in which the user can enter custom symbol paths.
My personal use case for this is to specify the lib_burst_generated.pdb that burst generates during compilation.

@bitsandfoxes
Copy link
Contributor

Hey @LukasKastern! Welcome and thanks for contributing! I'm curious: Where does lib_burst_generated.pdb end up that you have to specify the path yourself? I just want to make sure that that's not a gap we have in general.

@LukasKastern
Copy link
Author

It's in two separate locations, next to the game executable and in ProjectName_BurstDebugInformation_DoNotShip.

I assumed it wouldn't be picked up because it wasn't directly referenced in the paths lists but after making another build without specifying it as an extra symbol path it looks like it's uploaded just fine.
Seems to just have been the same issue as the one that #655 fixed.

On a different note, the pdb is uploaded fine but the .dll is missing. I'm getting A required debug information file was missing. lib_burst_generated.dll in the dashboard. Is that actually an issue or can this be safely ignored?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants