[Bug 52124] New: immediate crash

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52124

Bug ID: 52124
           Summary: immediate crash
           Product: Wine
           Version: 6.0.2
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 71158
  --> https://bugs.winehq.org/attachment.cgi?id=71158
crash report + ls of program directory

Hi guys !

Experiencing some difficulties installing Walsalva Wave Pro 2.0 with wine.

About the program: Valsalva is a program to analyze breath, more precisely how
breath and blood circulation interact. (see here for more details:
https://coherentbreathingbiofeedback.com/) The present 2.0 version has been
launched in the W7 time-frame. Valsalva runs on about 10.000 computers and is
running without issue on XP, Vista, 7, 8, 10, & 11.

But not on my "stable" Debian computer (bullseye version) ;)

Not aware of having done anything special ;)

What can I do ?

All help is welcome !

Best, Matt

Enclosed a crash-report, and thereafter a list of the installed files

[Bug 52124] Valsalva Wave Pro 2.0 crashes immediately

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52124

Louis Lenders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|immediate crash             |Valsalva Wave Pro 2.0
                   |                            |crashes immediately
                 CC|                            |[e-mail]

--- Comment #1 from Louis Lenders  ---
Hi
> What can I do ?
> All help is welcome !

- Try upgrade from wine-6.0.2 to current wine-6.22

- Please add console output before the crash to this bugreport

- You could also try run with: WINEDEBUG=+relay,+seh wine
"C:\users\mathias\Desktop\COHERENCE Valsalva Wave Pro 2.0\Valsalva Wave Pro
2.0.exe" &>log.txt and attach bzipped2 compressed log.txt to this bugreport.
Maybe it reveals something

Regards