October 2007 - Wine-Devel - list.winehq.org

[AppDB] Fix maintainer processing
by Alexander Nicolaysen Sørnes Oct. 21, 2007

Oct. 21, 2007

Fix maintainer processing Alexander N. Sørnes

1 0

msi testing
by EA Durbin Oct. 20, 2007

Oct. 20, 2007

I recently purchased the book "The Definitive Guide to Windows Installer". I haven't really started reading it yet, but the source code and sample files are available online so I starting testing the sample .msi files in wine and windows out of curiousity . These files are relatively small and are targeted to demonstrate specific .msi functionality. They might work nicely for testing installer functionality in wine without being obscured by large amounts of other application related debug output. http://www.apress.com/book/downloadfile/1645 _________________________________________________________________ Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmail…

1 0

Re: gdi32: fix unchecked NULL ptr and off by one error in BIDI_Reorder
by Michael Stefaniuc Oct. 20, 2007

Oct. 20, 2007

Hello Alexander! Alexander Dorofeyev wrote: > This patch fixes two problems that are causing crashes in Thanks for the patch. Could you please split the patch in two; one patch for each problem fixed. Please also do not use C++ style comments aka // > BIDI_Reorder. In particular, Skype 3.5.0 crashed every time I type > anything in the chat edit box. > > One problem is that it wasn't assured lpOutString isn't NULL, and NULL > was getting passed to this routine by GetCharacterPlacementW. so it was > crashing in memcpy. This patch creates a temporary buffer when > lpOutString is NULL and it is used for in-place modifications instead in > such case. > > Another is off by one error in setting lpOrder. > > --- > dlls/gdi32/bidi.c | 33 ++++++++++++++++++++++++++++----- > 1 files changed, 28 insertions(+), 5 deletions(-) > > > ------------------------------------------------------------------------ > > diff --git a/dlls/gdi32/bidi.c b/dlls/gdi32/bidi.c > index cac9453..2b1320e 100644 > --- a/dlls/gdi32/bidi.c > +++ b/dlls/gdi32/bidi.c > + > + if (!lpOutString) > + { > + //temporary buffer was created > + HeapFree(GetProcessHeap(), 0, lpReorderBuffer); > + } > + > return TRUE; > } thanks bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 Sr. Network Engineer Fax.: +49-711-96437-111

1 0

Solidworks 2007 Test with 0.9.47
by Stephan Rose Oct. 20, 2007

Oct. 20, 2007

Major improvement with Solidworks 2007 on the latest version. Visually, everything actually looks perfect now. OpenGL windows are where they are supposed to be. Font is right. So from that end, everything appears to work very well. What's still broken: - Performance is extremely bad. Even on my Dual Core with 4 gigs of RAM. - Memory usage is extremely high still at around 2 gigs. - Extrude function, first thing I test as it's the most fundamental, still won't work. CPU will just go to full load on that core and just sit there forever. Infinite loop maybe? Definite improvement though, thanks everyone. =) Stephan

1 0

winmm test runs forever?
by Dan Kegel Oct. 19, 2007

Oct. 19, 2007

Today I'm starting to see winmm_test spew an infinite series of failures on line 467 of mixer.c: ../../../tools/runtest -q -P wine -M winmm.dll -T ../../.. -p winmm_test.exe.so mixer.c && touch mixer.ok ALSA lib seq_hw.c:456:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory mixer.c:359: Test failed: mixerGetDevCapsA: MMSYSERR_NOERROR expected, got MMSYSERR_BADDEVICEID mixer.c:364: Test failed: mixerGetDevCapsA: MMSYSERR_NOERROR expected, got MMSYSERR_BADDEVICEID mixer.c:408: Test failed: mixerGetLineInfoA(MIXER_GETLINEINFOF_DESTINATION): MMSYSERR_INVALPARAM or MIXERR_INVALLINE expected, got MMSYSERR_BADDEVICEID mixer.c:433: Test failed: mixerGetLineInfoA(MIXER_GETLINEINFOF_DESTINATION): MMSYSERR_NOERROR expected, got MMSYSERR_BADDEVICEID mixer.c:467: Test failed: mixerGetLineInfoA(MIXER_GETLINEINFOF_SOURCE): MMSYSERR_NOERROR expected, got MMSYSERR_BADDEVICEID mixer.c:467: Test failed: mixerGetLineInfoA(MIXER_GETLINEINFOF_SOURCE): MMSYSERR_NOERROR expected, got MMSYSERR_BADDEVICEID mixer.c:467: Test failed: mixerGetLineInfoA(MIXER_GETLINEINFOF_SOURCE): MMSYSERR_NOERROR expected, got MMSYSERR_BADDEVICEID mixer.c:467: Test failed: mixerGetLineInfoA(MIXER_GETLINEINFOF_SOURCE): MMSYSERR_NOERROR expected, got MMSYSERR_BADDEVICEID ... I have to do wineserver -k to make progress.

2 2

Make test drill, next steps, call for help with Winetest
by Jeremy White Oct. 19, 2007

Oct. 19, 2007

Hi Folks, So I had plan to report on the status of make test, and sound a call to action. That is, one of the best and most fun things we did at Wineconf was to call bullshit on the failure of make test to work reliably. That is, it only runs cleanly on Alexandre's machine, and not even all the time then. So, we worked hard to make 'make test' work reliably on other folks systems at Wineconf. We made a lot of progress; cutting failures by half, I would say. The closest we got was with Michael; I think he was down to 3 at the end. However, we're still plagued with differences due to chipsets, locales, and other differences. But I think it is vital that we continue this work. The fact that 'make test' doesn't work anywhere, really, is bullshit. However, I'm enough of a weasel that I wanted to get out of collating all of this data myself. So I investigated (or tried to investigate) winetest to see if I could dump this work on a tool. And it looks like it would be great. Of course, with a few caveats :-/. In my opinion, it needs the following: 1. A Wiki page! I could not find *any* documentation on this utility. For example, I'm still not entirely clear on how to setup and/or register my build.id so that my results are available on the web site. (And the rather non intuitive requirement to 'know' the unpublished url http://test.winehq.org/data/ is harsh). 2. Headless operation From my experiments, there were a number of dialogs I had to dismiss, and some worrying complaints in unpacking msvcrtd and msvcrt tests. This second point is probably a bit less important than the first. However, it looked like if just a few little glitches could be ironed out, that it would be a fantastic tool for working on the make test problem. We'd be able to see the common failures, and work to resolve them and drive them to zero. Is there someone that could do the first part of this? Just document what is already there? Or point me to the page that exists that I just missed? Cheers, Jeremy

4 8

Re: D3DX8: [4/13]: implement D3DX__Add with a test
by Stefan Dösinger Oct. 19, 2007

Oct. 19, 2007

Am Freitag, 19. Oktober 2007 10:13:39 schrieb David.Adam(a)math.cnrs.fr: > +#define expect_vec3(expectedvec,gotvec) ok((fabs(expectedvec.x-gotvec.x)<admitted_error)&&(fabs(expectedvec.y-gotvec.y)<admitted_error)&&(fabs(expectedvec.z-gotvec.z)<admitted_error),"Expected Vector= (%f, %f,%f)\n , Got Vector= (%f, %f, %f)\n", expectedvec.x, expectedvec.y, expectedvec.z, gotvec.x, gotvec.y, gotvec.z); Usually inline functions are prefered over macros. I don't know how well that works with ok though, since it might drop the line of the error and make debugging harder.

1 0

Re: D3DX8: [1/13] resent: implement D3Dx__Length with a test
by Stefan Dösinger Oct. 19, 2007

Oct. 19, 2007

Am Freitag, 19. Oktober 2007 10:10:07 schrieb David.Adam(a)math.cnrs.fr: > ----- > Pièces jointes (Les liens expireront le May 1, 2008) > https://webmail.math.cnrs.fr/horde/imp/attachment.php?u=dadam%40math.cnrs.f >r&t=1192788607&f=0001-Implement-D3DX___Length-function-with-a-test.patch.pat >ch Did you forget to attachthe file?

1 0

Use warn+heap when running 'make test'
by Dan Kegel Oct. 19, 2007

Oct. 19, 2007

As noted in http://bugs.winehq.org/show_bug.cgi?id=9916 using warn+heap poisons free memory, and finds a few more bugs. People who run 'make test' should consider running WINEDEBUG=warn+heap make test instead. (I don't know whether we should make that the default, though. Anyone have an opinion?)

2 1

Re: wined3d: Fix resource cleanup if CreateCubeTexture fails.
by Stefan Dösinger Oct. 19, 2007

Oct. 19, 2007

Am Freitag, 19. Oktober 2007 07:14:17 schrieb Allan Tong: Looks good to me

1 0