Skip to content

libobs: Add module version number to Windows crash handler#13190

Open
exeldro wants to merge 1 commit intoobsproject:masterfrom
exeldro:crash_module_version
Open

libobs: Add module version number to Windows crash handler#13190
exeldro wants to merge 1 commit intoobsproject:masterfrom
exeldro:crash_module_version

Conversation

@exeldro
Copy link
Contributor

@exeldro exeldro commented Mar 4, 2026

Description

Add module version number to Windows crash handler

Motivation and Context

Want to know if the users used the latest version to get the crash
example:
00007FFFB8D30000-00007FFFB8D42000 C:\git\obs-studio\build_x64\rundir\RelWithDebInfo\obs-plugins\64bit\3d-effect.dll (0.1.4.0)

How Has This Been Tested?

On Windows 11 by crash

Types of changes

  • New feature (non-breaking change which adds functionality)

Checklist:

  • My code has been run through clang-format.
  • I have read the contributing document.
  • My code is not on the master branch.
  • The code has been tested.
  • All commit messages are properly formatted and commits squashed where appropriate.
  • I have included updates to all appropriate documentation.

}

struct win_version_info ver = {0};
if (get_dll_ver(module_name, &ver)) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

get_dll_ver calls bmalloc which is unsafe to use in a crashing path (crash could be due to OOM).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The dstr calls in this function also use brealloc, should that all be refactored? And if so that would be something for a separate pull request in my opinion.

@WizardCM WizardCM added the New Feature New feature or plugin label Mar 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

New Feature New feature or plugin

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants