https://bugs.winehq.org/show_bug.cgi?id=37841
Bug ID: 37841
Summary: Checking wine for errors with PVS
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aa-c-aa(a)mail.ru
Distribution: ---
ENGLISH: http://www.viva64.com/en/b/0272/
RUSSIAN: http://habrahabr.ru/company/pvs-studio/blog/233179/
there is many misstakes and errors
--
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=37098
Bug ID: 37098
Summary: Checking Wine with PVS-Studio and Clang Static
Analyzer
Product: Wine
Version: 1.7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nick.smallville(a)gmail.com
Hello, I checked out the Wine using two static analyzers(Clang Static Analyzer
&& PVS-Studio) in the openSUSE 13.1. In my article, I described the errors
found: http://www.viva64.com/en/b/0272/
--
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=37825
Bug ID: 37825
Summary: Keybinding to write to stderr
Product: Wine
Version: 1.7.33
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sworddragon2(a)aol.com
Distribution: ---
For some of my bug reports I'm providing logs that contain the output from Wine
in the case there appears an error that gives a hint. But I'm noticing one
problem with this: Until the point there the bug can be reproduced the log does
often get spammed with many things that are unrelated to the targeted bug. So I
was thinking that it could be helpful for debugging if we could bind an action
to a key combination that does for example write the timestamp to stderr. With
such a feature it would be possible to use the keybinding directly before and
after the bug appears. This would make it easier to see the related lines on
the Wine output that could be responsible for the targeted 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=37821
Bug ID: 37821
Summary: Wisterer HX freeze on sunday event
Product: Wine
Version: 1.7.33
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sweepers(a)gmx.de
Distribution: ---
Created attachment 50371
--> https://bugs.winehq.org/attachment.cgi?id=50371
console log calling "wine wistererhx.exe"
Hi,
found a problem in windows application "Wisterer HX" Version 4.2.32
It's a lightweight software for calendar management, diary, adress database,
schedule and birthday reminder etc.
Unfortunately only available in german, but i'll try to translate...
Homepage is http://www.wisterer.de but the download is redirected to other
sites.
download zip with setup exe:
http://www.chip.de/downloads/Wisterer-HX_13002426.html
After running setup.exe, the application complains about missing dlls.
I got it starting up by copying these files from win7 x64 directory
C:\Windows\SysWOW64
to ~/.wine/drive_c/Program Files (x86)/Wisterer HX
ab412429f1e5fb9708a8cdea07479099 COMDLG32.OCX
8bbc59ae8497d0bbee8d66b74c7db971 mfc40.dll
ae47a8a5fe8193bb84ffcd338115d8ef MSCOMCT2.OCX
e52859fcb7a827cacfce7963184c7d24 MSCOMCTL.OCX
4dc9752ba6418bbac12852bbcf0374cb MsgHoo32.OCX
9618e4752b19ce24efd729c662c8db1e msvbvm60.dll
045a16822822426c305ea7280270a3d6 Richtx32.ocx
download zip with portable version:
http://www.computerbild.de/download/Wisterer-HX-Portable-2775828.html
51f4e5042c7a71ace966d0b47c080eb0 portablewistererhx.zip
This zip contains partly different versions of dlls above, but problem is the
same.
While with Wine 1.6.2 program crashed when clicking on "Anzeige ->
Monatsanzeige Liste" (view full month),
this is now fixed with latest version Wine 1.7.33 - thanks for that :)
But one problem remains: go to "Kalender" -> "Neues Ereignis eingeben" (enter
new event)
then select the tab "monatlich" (monthly) find "Mittwoch" (wednesday) in the
drop down menu. Only if "Sonntag" (sunday) is selected, the app freezes, 100%
CPU.
This action prepares an event to be scheduled every first sunday each month, so
obviously some problem with day of week calculation.
Same happens if an existing calendar file Kalender.wik is opened that contains
sunday events.
Thank you!
--
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=5137
Bruno Jesus <00cpxxx(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Fixed by SHA1| |d28c40da3bc685241363370f4b4
| |86bd975396afc
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #18 from Bruno Jesus <00cpxxx(a)gmail.com> ---
Fixed by:
http://source.winehq.org/git/wine.git/commitdiff/d28c40da3bc685241363370f4b…
--
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=6955
JHaleIT <jhaleit(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jhaleit(a)gmail.com
--- Comment #144 from JHaleIT <jhaleit(a)gmail.com> ---
I can confirm that this bug exist in the latest version of Wine in WineBottler
for Phantasy Star Universe.
--
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=5908
Anastasius Focht <focht(a)gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Fixed by SHA1| |497b67dbf623e8aacb2eaaaa326
| |a5782eb3c06d8
CC| |focht(a)gmx.net
Component|shell32 |wintrust
Hardware|Other |x86
Version|unspecified |0.9.18.
OS|other |Linux
--
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=37127
Bug ID: 37127
Summary: PVS-Studio Error: Unreliable tests
Product: Wine
Version: 1.7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lukebenes(a)hotmail.com
PVS-Studio identifies Unreliable tests. Some of the modules' folders contain
the test folder with source files for tests. Debug information is printed
through the 'ok' macro. Here are a few suspicious fragments:
V501 There are identical sub-expressions to the left and to the right of the
'==' operator: ddsd3.lpSurface == ddsd3.lpSurface dsurface.c 272
...
ok(ddsd3.lpSurface == ddsd3.lpSurface, //<==
"lpSurface from GetSurfaceDesc(%p) differs\
from the one returned by Lock(%p)\n",
ddsd3.lpSurface, ddsd2.lpSurface); //<==
...
It very much looks like a typo. I suspect this code should compare the same
variables that are printed.
V502 Perhaps the '?:' operator works in a different way than it was expected.
The '?:' operator has a lower priority than the '==' operator. url.c 767
...
ok(size == no_callback ? 512 : 13, "size=%d\n", size);
...
The precedence of the "==" operator is higher than that of '?:', so the size
variable is not compared to the values 512 and 13. The expression is always
true as it evaluates either to 512 or 13, which means this check doesn't check
anything.
Other similar fragments:
V502 Perhaps the '?:' operator works in a different way than it was
expected. The '?:' operator has a lower priority than the '==' operator.
string.c 1086
V502 Perhaps the '?:' operator works in a different way than it was
expected. The '?:' operator has a lower priority than the '==' operator.
string.c 1111
V502 Perhaps the '?:' operator works in a different way than it was
expected. The '?:' operator has a lower priority than the '==' operator.
reader.c 761
V502 Perhaps the '?:' operator works in a different way than it was
expected. The '?:' operator has a lower priority than the '==' operator.
protocol.c 2928
V502 Perhaps the '?:' operator works in a different way than it was
expected. The '?:' operator has a lower priority than the '==' operator. dde.c
1594
V502 Perhaps the '?:' operator works in a different way than it was
expected. The '?:' operator has a lower priority than the '==' operator.
reader.c 761
details on the V501 error here: http://www.viva64.com/en/d/0090/
details on the V502 error here: http://www.viva64.com/en/d/0091/
--
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=37126
Bug ID: 37126
Summary: PVS-Studio Error: Printing the result of identical
functions
Product: Wine
Version: 1.7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lukebenes(a)hotmail.com
PVS-Studio identifies Printing the result of identical functions Error,V681.
The language standard does not define an order in which the 'tlb_read_byte'
functions will be called during evaluation of arguments. tlb.c 650
...
printf("\\%2.2x \\%2.2x\n", tlb_read_byte(), tlb_read_byte());
...
According to the C++ language standard, the sequence of computing a function's
actual arguments is not defined. Which function will be called first depends on
the compiler, compilation parameters, etc.
details on the V681 error here: http://www.viva64.com/en/d/0315/
--
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.