http://bugs.winehq.org/show_bug.cgi?id=7641
------- Additional Comments From rmay(a)ou.edu 2007-06-03 16:39 -------
Not really, I'm just working with a program in which I'm interested. Given what
Dan Kegel said above, I'm leaning towards the lack of the init being the problem
with the new version. Given that, I'd think all that's necessary is a test
program that just creates the datetime control w/o init -- if this works on
windows, then that might be it.
In talking with the developer, he said there was a change in the winver variable
at one time to target win2k instead of 98. Could this cause a lack of a call to
init?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7643
liquitsnake(a)gmx.net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |liquitsnake(a)gmx.net
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7643
------- Additional Comments From liquitsnake(a)gmx.net 2007-06-03 16:38 -------
For the crashes I get this:
err:seh:setup_exception stack overflow 208 bytes in thread 000a eip 7b86ca0f esp
7943df30 stack 0x7943e000-0x7964d000
Yeah, my Wine loves to stack-overflow..
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7641
------- Additional Comments From thestig(a)google.com 2007-06-03 16:30 -------
Can you write a simple program that just creates the datetime picker the same
way as weatherscope to recreate the problem?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7235
------- Additional Comments From bdonlan(a)gmail.com 2007-06-03 16:30 -------
Setting the second parameter to NULL returns the C locale. By my reading of the
manpage, setlocale() will not respect environment variables at all unless called
with an empty string:
If locale is "", each part of the locale that should be modified is set
according to the environment variables. The details are implementation
dependent. For glibc, first (regardless of category), the environment
variable LC_ALL is inspected, next the environment variable with the
same name as the category (LC_COLLATE, LC_CTYPE, LC_MESSAGES, LC_MONE‐
TARY, LC_NUMERIC, LC_TIME) and finally the environment variable LANG.
The first existing environment variable is used. If its value is not a
valid locale specification, the locale is unchanged, and setlocale()
returns NULL.
and
If locale is NULL, the current locale is only queried, not modified.
On startup of the main program, the portable "C" locale is selected as
default. A program may be made portable to all locales by calling set‐
locale(LC_ALL, "" ) after program initialization, by using the values
returned from a localeconv() call for locale-dependent information, by
using the multi-byte and wide character functions for text processing
if MB_CUR_MAX > 1, and by using strcoll(), wcscoll() or strxfrm(),
wcsxfrm() to compare strings.
Therefore, if wine merely calls setlocale(LC_*, NULL), it is incorrect. It must
call locale(LC_ALL, "") during initialization.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4790
------- Additional Comments From rmh(a)aybabtu.com 2007-06-03 16:19 -------
Created an attachment (id=5260)
--> (http://bugs.winehq.org/attachment.cgi?id=5260&action=view)
winedbg backtrace
A backtrace reveals that FPE happened during SSE division. Code is preceded by:
7a0fd9: 0f 57 c0 xorps %xmm0,%xmm0
7a0fdc: 0f 10 4d d0 movups 0xffffffd0(%ebp),%xmm1
7a0fe0: 0f 5e c8 divps %xmm0,%xmm1
Since I can't print %xmm1 directly, I printed its copy in $ebp+0xffffffd0.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7641
------- Additional Comments From rmay(a)ou.edu 2007-06-03 15:29 -------
Trace for Weatherscope 1.4.1 shows:
trace:commctrl:DllMain 0x7ece0000,8,(nil)
trace:commctrl:DllMain 0x7ece0000,1,0x1
trace:commctrl:DllMain Subclassing atom added: 0xc012
trace:commctrl:InitCommonControlsEx (0x0000032f)
For Weatherscope 1.5b:
trace:commctrl:DllMain 0x7ece0000,8,(nil)
trace:commctrl:DllMain 0x7ece0000,1,0x1
trace:commctrl:DllMain Subclassing atom added: 0xc012
So it looks like there is a lack of an InitCommonControls in the new (and
crashing) version. Can anyone help me with a conformance test and/or patch to
make wine do the right thing? I would try, but I'm definitely no win32 API expert.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7235
------- Additional Comments From julliard(a)winehq.com 2007-06-03 15:05 -------
The second call should be setlocale(LC_CTYPE,NULL) to mimic the Wine behavior.
Does this work for you in your test app?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5253
------- Additional Comments From iod(a)mailinator.com 2007-06-03 15:01 -------
~~~~~~~~~~~~~~~~FIXED~~~~~~~~~~~~~~~~~~~~
To overcome this problem you need to install some components to Wine.
Use WineTools to install them (I use version 0.9.12).
You can get WineTools here: http://www.von-thadden.de/Joachim/WineTools/
In the "Base Setup" menu install:
1. "TrueType Font Arial"
2. "DCOM98"
3. "Microsoft Foundation Clases 4.0"
4. "Internet Explorer 6.0 SP1" (twice, if needed)
Tada... Battle.net works and you can join games with Wine
IOD
I posted a picture to prove it works on battle.net here:
http://appdb.winehq.org/appimage.php?iId=5888
To see the test data I got: http://appdb.winehq.org/appview.php?
iVersionId=149&iTestingId=8748
~~~~~~~~~~~~~~~~FIXED~~~~~~~~~~~~~~~~~~~~
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.