Sentry not associating stacktrace with corresponding uploaded Windows pdb

[GeckoEidechse]

Environment

SaaS (https://sentry.io/)

Version

No response

Link

No response

DSN

https://f833732deb2240b0b2dc4abce97d0f1d@o1374052.ingest.sentry.io/6692177

Steps to Reproduce

1. Create a Rust project according to the docs
2. Create a release build (cargo release) and publish it somewhere
3. Upload the pdb to sentry by running .\sentry-cli upload-dif -o YOUR_ORG_HERE -p YOUR_PROJECT_HERE .\app.pdb
4. Cause a panic in your Rust application and have the Sentry crash logger upload the stacktrace
5. Check the crash in sentry dashboard

Expected Result

Actual Result

[getsantry]

Assigning to @getsentry/support for routing, due by Monday, February 27th at 5:00 pm (sfo). ⏲️

[GeckoEidechse]

Additional notes:

As far as I can tell reading through the docs, Sentry is able to automatically associate a stacktrace with a pdb so to my knowledge I do not need to tell it which pdb to use for a given stacktrace (not that I found an option to do that).

Placing the app.pdb next to the Windows exe, and running and crashing it I do get the corresponding information from the pdb shown in Sentry so I believe the issue is outside of Rust or Sentry failing to upload any specific information but rather the backend server being unable to associate the uploaded pdb with a stacktrace

[getsantry]

Routing to @getsentry/ingest for triage, due by Wednesday, March 1st at 17:00 (vie). ⏲️

[getsantry]

Routing to @getsentry/owners-stacktrace for triage, due by Wednesday, March 1st at 12:19 pm (sfo). ⏲️

[Swatinem]

This looks a little bit like no module list was provided. We only recently made this a default feature in the Rust SDK: https://github.com/getsentry/sentry-rust/blob/master/CHANGELOG.md#0293
Which version are you using, and are you setting explicit feature flags?

[GeckoEidechse]

Hilariously I was on v0.29.2 when running the test, i.e. one dot release too early. I'll retest with a higher version when I get to it later today and try and see if it resolves the issue.

For reference, here's my

• Cargo.toml
• main.rs where Sentry is initialised