https://bugs.winehq.org/show_bug.cgi?id=42731
Bug ID: 42731
Summary: stack overflow when .bat script variable has more than
256 characters
Product: Wine
Version: 2.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lucianposton(a)gmail.com
Distribution: ---
Created attachment 57723
--> https://bugs.winehq.org/attachment.cgi?id=57723
bug demo
When a variable with more than (roughly) 256 characters in a .bat script is
passed as a parameter, the script fails with the following error:
err:seh:setup_exception_record stack overflow 1408 bytes in thread 0009 eip
7bc4887d esp 00240db0 stack 0x240000-0x241000-0x340000
attached .bat file that demonstrates the bug
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49643
Bug ID: 49643
Summary: Calling ClipCursor too frequently can cause stack
overflow in foreground window thread.
Product: Wine
Version: 5.13
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: rbernon(a)codeweavers.com
Distribution: ---
Created attachment 67845
--> https://bugs.winehq.org/attachment.cgi?id=67845
Reproducing sample application
Calling ClipCursor too frequently in a non-foreground thread may cause the
foreground window thread to overflow its stack. This is happening under some
circumstances with CoD: WWII.
This is inherent to the current implementation where every ClipCursor request
from a non-foreground thread involves synchronously sending internal messages
to the foreground window thread, then to the desktop thread. Each ClipCursor
request is processed when the desktop thread is notified, growing the stack
every time, until it overflows.
The attached program can be used to easily reproduce the issue.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44061
Bug ID: 44061
Summary: Destiny 2 crashes on launch
Product: Wine
Version: 2.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zombieff(a)gmail.com
Distribution: ArchLinux
Created attachment 59774
--> https://bugs.winehq.org/attachment.cgi?id=59774
Crash report shown by the app
The game "Destiny 2" crashes on launch.
It installs successfully via Blizzard client, but crashes on launch.
There's a delay between "Launching" → "Ready to Launch" (not launched) →
crashed with an error.
Tested on Arch Linux.
Wine version is wine-2.21 (Staging).
Terminal output (app crash report is in the attachment):
fixme:thread:create_user_shared_data_thread Creating user shared data update
thread.
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:crypt:CRYPT_LoadProvider Failed to load dll
L"C:\\windows\\system32\\rsaenh.dll"
fixme:seh:call_stack_handlers nested exception
wine: Unhandled exception 0xc06d007e in thread 556 at address 0x7b450c67
(thread 0556), starting debugger...
fixme:module:load_dll Loader redirect from L"uxtheme.dll" to L"uxtheme-gtk.dll"
fixme:module:load_dll Loader redirect from L"uxtheme.dll" to L"uxtheme-gtk.dll"
fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
fixme:uxthemegtk:SetWindowTheme (0xf0054, (null), (null))
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49982
Bug ID: 49982
Summary: A '(call )' line does not reset %ERRORLEVEL% to 0
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: aa1ronham(a)gmail.com
Distribution: ---
The following batch script:
```
@echo off
echo Initial error level: %errorlevel%
call missing
echo After bad call: %errorlevel%
(call )
echo After empty call: %errorlevel%
```
gives the following output under Wine:
```
Initial error level: 0
Can't recognize 'missing' as an internal or external command, or batch script.
After bad call: 1
After empty call: 1
```
However, Windows 10 gives the following output:
```
Initial error level: 0
'missing' is not recognized as an internal or external command,
operable program or batch file.
After empty call: 1
After empty call: 0
```
It looks like the Windows cmd.exe resets %errorlevel% to 0 after a '(call )' is
executed, while Wine's cmd.exe leaves it unchanged.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49774
Bug ID: 49774
Summary: macDriver no longer functions within macOS VM
Product: Wine
Version: 4.15
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winemac.drv
Assignee: wine-bugs(a)winehq.org
Reporter: gcenx83(a)gmail.com
Regression SHA1: 792521f33b2786cb100cb202dcb4181a579ef3b3
Wine-4.14 macDriver would function within a macOS VM from Wine-4.15 that’s no
longer the case.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49172
Bug ID: 49172
Summary: Always true condition `code > 0xffff` in
vbscript/global.c
Product: Wine
Version: 5.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: mikrutrafal54(a)gmail.com
Distribution: ---
code > 0xffff is always true - probably code > 0 should look like code < 0
https://github.com/wine-mirror/wine/blob/59987bc9ecdd0dbafd768a95c21a14884b…
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47570
Bug ID: 47570
Summary: FotoBizX - Installer throws backtrace
Product: Wine
Version: 4.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 64971
--> https://bugs.winehq.org/attachment.cgi?id=64971
Backtrace (4.11 Staging)
Hello everyone,
I have been trying out FotoBizX which is a business software for photographers
and agencies allowing invoices and quotes.
There is a demo version available at:
https://www.cradocfotosoftware.com/fotobiz/fotobiz-x-demo
sha256sum installfotoBizX1005.exe
7f6bcc85413442e4fe4f61919a98e0fffbcef32f2d99272abec9fe0dec0adffd
installfotoBizX1005.exe
Will try to add an AppDB entry later on.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49309
Bug ID: 49309
Summary: vbscript:run test fails in Japanese locale
Product: Wine
Version: 5.9
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Distribution: ---
For example:
https://test.winehq.org/data/48020f4846cca1a02f4e1dc037e2cc2068df5e9c/linux…
run.c:1877: Error in line 1585: 0 L"Invalid procedure call or argument"
run.c:1891: Test failed: unexpected call OnScriptError
run.c:2943: Test failed: expected global_success_d
run.c:2944: Test failed: expected global_success_i
run.c:2946: Test failed: parse_script failed: 800a0005
It seems that the call testAsc(Chr(255), 255) causes a runtime error when Asc
is called with Chr(255). For some reason, on the Japanese locale, this Chr call
gives us U+F8F3. It makes sense to get different results depending on encoding,
but I don't understand why we get this one.
Since this hasn't been observed on Windows, I assume this is a bug in Wine's
vbscript and not the test.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.