http://bugs.winehq.org/show_bug.cgi?id=33307
Bug #: 33307
Summary: heap corruption with gcc 4.8.0
Product: Wine
Version: 1.5.27
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lich(a)math.spbu.ru
Classification: Unclassified
Fresh wine compiled with gcc 4.8.0 is quite unusable. Likely, gcc is a culprit.
But nevertheless it might indicate to some very sophisticated hidden bug in
wine64, so I post a bug here.
Compilation:
$ cd wine
$ mkdir build64
$ cd build64
$ ../configure --enable-win64 --prefix=/opt/wine64 --without-xinput2
--disable-tests
$ sudo make install
$ wine64 notepad
Bus error
Further investigation has led to the following:
$ WINEDEBUG=file,ntdll,heap wine64 notepad
...
err:heap:HEAP_ValidateInUseArena Heap 0x10000: block 0x106c0 tail overwritten
at 0x106e8 (byte 0/32 == 0x5c)
.....
wine64: ../../../dlls/ntdll/heap.c:455: HEAP_GetPtr: Assertion `0' failed.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=28050
Summary: llvm-gcc-4.5 fails to compile loader/preloader.c with
optimizations enabled
Product: Wine
Version: 1.3.26
Platform: x86
URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=63718
2
OS/Version: Linux
Status: NEW
Keywords: download, source
Severity: blocker
Priority: P2
Component: loader
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
austin@debian:~/wine-git/loader$ make
llvm-gcc -o wine-preloader -static -nostartfiles -nodefaultlibs
-Wl,-Ttext=0x7c400000 preloader.o ../libs/port/libwine_port.a
preloader.o: In function `set_process_name':
/home/austin/wine-git/loader//preloader.c:455: undefined reference to `memset'
preloader.o: In function `map_so_lib':
/home/austin/wine-git/loader//preloader.c:455: undefined reference to `memset'
collect2: ld returned 1 exit status
make: *** [wine-preloader] Error 1
make -k lets it compile and wine runs. Alternatively, you can disable
optimization in loader/Makefile, and it will compile.
I tried a simple patch:
diff --git a/loader/preloader.c b/loader/preloader.c
index a94c52c..2e55d2a 100644
--- a/loader/preloader.c
+++ b/loader/preloader.c
@@ -173,6 +173,9 @@ void *__stack_chk_guard = 0;
void __stack_chk_fail_local(void) { return; }
void __stack_chk_fail(void) { return; }
+/* for dragonegg */
+void *memset(void *s, int c, size_t n) { return s; }
+
#ifdef __i386__
/* data for setting up the glibc-style thread-local storage in %gs */
but then wine segfaults :/. Additionally, using a simple implementation:
(from http://clc-wiki.net/wiki/C_standard_library:string.h:memset)
void *memset(void *s, int c, size_t n)
{
unsigned char* p=s;
while(n--)
*p++ = (unsigned char)c;
return s;
}
fails in the same way.
This is the only failure with llvm-gcc-4.5 (aka dragonegg), after that, at
least noteapd runs. Haven't checked what tests fail yet though :)..
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=33521
Bug #: 33521
Summary: Compilation fails with GCC 4.8 -O3
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jeff(a)deseret-tech.com
Classification: Unclassified
WINE compilation fails with ArchLinux's GCC 4.8.0-4 (currently in testing).
preloader.o: In function `map_so_lib':
preloader.c:(.text+0x9e8): undefined reference to `memset'
preloader.o: In function `wld_start':
preloader.c:(.text+0x28d9): undefined reference to `memset'
collect2: error: ld returned 1 exit status
make[1]: *** [wine-preloader] Error 1
The distro-specific package is relevant because the codebase used is actually a
snapshot of version control taken on 2013 May 2, which includes the patch
discussed in bug #33307.
Compare bug #28050, regarding the same error, manifest in LLVM w/ dragonegg and
GCC 4.5. See http://llvm.org/bugs/show_bug.cgi?id=11173 for information on
that. Don't see an appropriate bug on GCC's tracker at the moment, not likely
to have time to create it.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=33455
Bug #: 33455
Summary: Tomb Raider (2013): Flickering Bushes with NVIDIA GPU
/ driver
Product: Wine
Version: 1.5.28
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: felixhaedicke(a)web.de
Classification: Unclassified
In a few forst game scenes, bushes with flickering leaves can be found.
I tested it on two computers with the following GPUs / drivers:
* NVIDIA GTX 560 Ti with proprietary driver 313.30 - Bug always reproducible
* Intel HD 3000 and driver version 2.21.6 - Bug NOT reproducible
What makes no difference:
* All effects on or off
* Lowest / highest deatil levels
* UseGLSL enabled disabled or
* StrictDrawOrdering enabled or disabled
I made a video of it here
http://youtu.be/9DONLEMEV3w
Unfortunately the video quality is not ideal and has a few distortions which
are caused by the record (used recordmydesktop), but the flickering should be
clearly visible.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=12504
Summary: TextOut shows only black rectangles and probably slows
down programme
Product: Wine
Version: 0.9.58.
Platform: Other
URL: http://www.makakgames.wz.cz
OS/Version: other
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: pavelvonlostice(a)seznam.cz
Game, which i have programmed uses function TextOut, but in wine there are only
black rectangles without text, and this game runs too slow. Its programmed by
using DirectDraw, so I use GetDC method. You can download it from
http://www.makakgames.wz.cz/static_objects/robo_bob%20install.exe
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=46635
Bug ID: 46635
Summary: git for windows works or crashes depending on how its
invoked
Product: Wine
Version: 4.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: paleozogt(a)gmail.com
Distribution: ---
Created attachment 63547
--> https://bugs.winehq.org/attachment.cgi?id=63547
wine git bug project
Git for Windows seems to work properly with Wine:
> ➜ wine git --version
> git version 2.20.1.windows.1
However, if its invoked via some other tool (such as CMake or Java) it will
crash. Perhaps it has to do with the particular API being used (evecvp, etc)?
For example, if CMake invokes it with
> execute_process(
> COMMAND git --version
> OUTPUT_VARIABLE VERSION
> OUTPUT_STRIP_TRAILING_WHITESPACE
> )
then we see:
> ➜ wine cmake .. -G "Unix Makefiles"
>003b:fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0x00000000>
>003b:fixme:winsock:WS_EnterSingleProtocolW unknown Protocol <0x00000000>
>wine: Unhandled page fault on write access to 0x00000000 at address 0x5db52b (thread 0045), starting debugger...
I've attached a project that allows you to reproduce this issue:
1) Make sure you have zip and p7zip-full installed
2) Setup wine with "wineboot"
3) Unzip the project and cd into it
4) Run ./setup.sh to download git, cmake, etc
5) Run ./test.sh to exercise 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=46541
Bug ID: 46541
Summary: WinToUSB Free latest version 64bit application error
message when starting
Product: Wine-staging
Version: 4.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: linards.liepins(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 63402
--> https://bugs.winehq.org/attachment.cgi?id=63402
terminal log
Attaching screenshot of the error and the terminal log.
--
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=38061
Bug ID: 38061
Summary: Nitro Family displays only a blank screen in full
screen
Product: Wine
Version: 1.7.36
Hardware: x86
URL: http://www.fileplanet.com/137999/download/Nitro-Family
-Demo
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: marc.bessieres(a)gmail.com
Distribution: ---
Created attachment 50702
--> https://bugs.winehq.org/attachment.cgi?id=50702
console output of Nitro Family demo full screen, blank screen
Hello,
Nitro Family displays only a blank screen in full screen.
Piotr Caban gave in bug 38050 the workaround of going into window mode by
pression Alt+Enter.
This allows to play the game.
So this is continuation of bug 38050, if you want the game not to crash you
need to be at least at commit b02934096d36a3c1e7f79fa73071b44e6bbb2c26 which is
post wine-1.7.36.
But the 7ac8ad4492eeaacca6909d2d96eb84aff05ca79c (also post wine-1.7.36) is
enough to show the issue.
I couldn't find this bug already reported, but I may have missed it.
All the bugs I found were about ddraw, and if I'm not mistaken this game
doesn't use it.
--- snip ---
> WINEDEBUG=+relay,+tid,+seh ~/wine-git/wine NitroFamily.exe >> log 2>&1
> grep ddraw log
>
> grep PE\ DLL log | cut -f2 -d, |cut -f2 -d\ |sort -u
L"advapi32.dll"
L"amx32.dll"
L"avifil32.dll"
L"comctl32.dll"
L"comdlg32.dll"
L"CrashRpt.dll"
L"crtdll.dll"
L"d3d8.dll"
L"dbghelp.dll"
L"dsound.dll"
L"Engine.dll"
L"Entities.dll"
L"Game.dll"
L"gdi32.dll"
L"ijl15.dll"
L"imm32.dll"
L"iphlpapi.dll"
L"KERNEL32.dll"
L"mmdevapi.dll"
L"msacm32.dll"
L"msvcp70.dll"
L"msvcr70.dll"
L"msvcrt.dll"
L"msvfw32.dll"
L"ntdll.dll"
L"ntoskrnl.exe"
L"ogg.dll"
L"ole32.dll"
L"oleaut32.dll"
L"opengl32.dll"
L"psapi.dll"
L"rpcrt4.dll"
L"Shaders.dll"
L"shell32.dll"
L"shlwapi.dll"
L"user32.dll"
L"userenv.dll"
L"uxtheme.dll"
L"version.dll"
L"vorbis.dll"
L"vorbisfile.dll"
L"windowscodecs.dll"
L"winealsa.drv"
L"wined3d.dll"
L"winejoystick.drv"
L"winex11.drv"
L"winmm.dll"
L"winspool.drv"
L"ws2_32.dll"
L"wsock32.dll"
--- snip ---
> sha1sum NitroFamily.exe
70144d05b75354f5f892f3afc760d991f69ef973 NitroFamily.exe
> du -hs NitroFamily.exe
1000K NitroFamily.exe
>
> ~/wine-git/wine --version
wine-1.7.36-15-g7ac8ad4
I'm attaching the command line output at
7ac8ad4492eeaacca6909d2d96eb84aff05ca79c because it is short
but I don't personally find anything suspicious.
This also happens with the demo
http://www.fileplanet.com/137999/download/Nitro-Family-Demo
> du -hs nitrofamilyoffdemo.exe
212M nitrofamilyoffdemo.exe
> sha1sum nitrofamilyoffdemo.exe
46082852a40592bf744778fd7212d79862900dd4 nitrofamilyoffdemo.exe
Cheers,
Marc
--
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.