Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extract debug information from Windows release builds #152

Open
matwey opened this issue Mar 29, 2020 · 1 comment
Open

Extract debug information from Windows release builds #152

matwey opened this issue Mar 29, 2020 · 1 comment
Assignees
Milestone

Comments

@matwey
Copy link
Owner

matwey commented Mar 29, 2020

No description provided.

@matwey matwey added this to the 3.5 milestone Mar 29, 2020
@ForNeVeR
Copy link
Collaborator

Currently, we have some kind of "debug" builds available, but I'm not sure they're usable at all: they seem to include our application built in debug mode (i.e. without some of the optimizations, and with additional asserts enabled), and linked with debug runtime libraries (not sure about Qt ones). This is barely useful for actual debug purposes.

The plan is:

  1. Eliminate separate debug builds (I'm not even sure we're allowed to redistribute debug versions of runtime binaries — though I'm not sure we're distributing them, but if we don't, then these builds are even more useless than I thought)
  2. Ensure we build and save PDBs for each release
  3. Pack the PDBs on the CI and make them a separate artifact on our CI
  4. Make sure our application is subject to Windows' automatic crash dump creation (I think it should work automatically, but if it isn't, then we better prepare some instructions on how to enable it)
  5. Make sure our PDBs really help to debug access violations

To perform steps 4-5, I plan to build a special binary that will always crash, and then try to create a crash dump and analyze it without PDBs, and then with them — the second should lead to properly formed stack traces and easier crash investigation.

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

No branches or pull requests

2 participants