Provide a Debug version, at least a version that can record call stack information when it crashes. To further track the problem of Windows client crash during synchronization.

#
### How to use GitHub

* Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are interested into the same feature.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.

---

## Feature request

**Which Nextcloud Version are you currently using:Rolling back from a version of 3.14 to 3.13

**Is your feature request related to a problem? Please describe.**
https://github.com/nextcloud/desktop/issues/7310
https://github.com/nextcloud/desktop/issues/7503
The problem started appearing in 3.14 but the recently released 3.15.0 still has this problem.

**Describe the solution you'd like**
The community seemed to have failed to locate and resolve the crash issue during file synchronization throughout version 3.14. You can consider providing a Debug version to directly record the call stack information when the client crashes, so that helpful information can be provided when problems occur.
At least the Github Release provides a Debug version, which will be removed after the problem is resolved. Otherwise the problem will become clueless.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

Review the linked crash reports (#7310 and #7503) first, then inspect the desktop client's Windows build and release configuration. Done means a debug artifact or crash call-stack collection path is available to help investigate synchronization crashes.

Written by the indexing model from the issue text.