wine-devel August 2011

wine-devel@winehq.org

86 participants
258 discussions

re: Where is the best place to report a fscanf bug found under wine-1.3.27?
by Dan Kegel 18 Sep '11

18 Sep '11

> Today I discovered .. that the scanf family of functions was > introducing float (32-bit floating-point) noise into double (64-bit > floating-point) results. I see it here, too: $ sudo apt-get install mingw32 $ i586-mingw32msvc-gcc test_fscanf.c $ echo "1.1e+01 1.1e+00 1.1e-01 1.1e-02 1.1e-03 1.1e-04" | ~/wine-git/wine a.exe 1.10000000000000000e+001 1.10000000000000009e+000 1.10000001639127737e-001 1.10000003278255491e-002 1.10000004917383261e-003 1.10000006556511075e-004 You can work around it with 'winetricks vcrun6', after which the test program outputs: 1.10000000000000000e+001 1.10000000000000010e+000 1.10000000000000000e-001 1.09999999999999990e-002 1.10000000000000010e-003 1.10000000000000000e-004 So the problem is in wine's msvcrt.dll. You could narrow it down further by printing out the raw byte strings for the numbers and then sprinking that printout through the path from when scanf is called to where printf returns. (Or, I suppose, step through it with a debugger instead.) But the best place to report the bug is http://bugs.winehq.org - Dan

2 2

re: Severe startup latencies for Windows applications run under wine
by Dan Kegel 17 Sep '11

17 Sep '11

Try oprofile instead. ( A really old intro is at http://www.winehq.org/wwn/249#oprofile%20&%20Wine )

4 4

buildbot status
by Dan Kegel 07 Sep '11

07 Sep '11

- stability problems The buildbot cluster is not ready for prime time yet. My ubuntu 11.04-based slaves tend to lock up within a day with either an OOM failure, an X livelock, or something else. So I brought an ubuntu 10.04.3 slave online and moved the buildmaster off onto its own machine; let's see what breaks next. - Slave speed Here is the complete build-and-test time (and the build time alone) for four CPUs: 54 (48) celeron @ 2.80 GHz (headless, so it's not running all tests) 17 (10) E8400 @ 3.00GHz 14 (6) Q9300 @ 2.50GHz 12 (4) i7 920 @ 2.67GHz I will probably stick with slaves that are core 2 duo or better, so patches can get fast feedback.

5 15

Re: kernel32: Fix writing to a pipe in WriteConsoleW().
by Eric Pouech 02 Sep '11

02 Sep '11

Le 03/08/2011 18:07, Francois Gouget a écrit : > WriteFile() checks if the handle corresponds to the console and if it > does invokes WriteConsoleA(). This barely escaped an infinite loop but > messed up the string encoding as CP_UNIXCP is usually different from > CP_ACP. > --- > > I noticed this issue while testing the net.exe tool. After making it > use WineConsole() I was getting the following outputs: > > $ wine net stop > Spécifie le service à arrêter. > $ ./wine net stop | cat > Sp├®cifie le service ├á arr├¬ter. > > It turns out that it's because we only get through the WineConsoleW() -> > WriteFile() -> WriteConsoleA() loop in the second case. could you elaborate a bit more. in case of wine ... | cat, the standard output should be a pipe not a console so writeconsoleW is supposed to fail so it would make more sense to simply let WriteConsoleW fail when is_console_handle(hConsoleOutput) is FALSE ? (similar functions as WriteConsoleA, ReadConsoleA/W should be protected the same way) A+ -- Eric Pouech "The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)

2 4

Re: 78217: Subject: [PATCH 3/3] winecfg: Remove driver selection from Audio tab
by Dan Kegel 01 Sep '11

01 Sep '11

On Wed, Aug 31, 2011 at 1:10 PM, <buildbot(a)buildbot.kegel.com> wrote: > The Buildbot has detected a failed build on builder runtests while building Wine. > Full details are available at: http://buildbot.kegel.com/builders/runtests/builds/161 > BUILD FAILED: failed git Something's fishy; looking at http://marc.info/?l=wine-patches&m=131134541100364&w=2 I see that the July 22nd version seems to have interesting strings, but the August 31st version has all question marks when it comes to non-ascii text. What happened between the two? http://source.winehq.org/patches/data/78217, which is where I pulled the patch from, also has the question marks.

2 2

Re: [PATCH 1/5] ddraw: Make the OpenGL renderer the default one.
by Stefan Dösinger 01 Sep '11

01 Sep '11

On Tuesday 30 August 2011 20:12:31 Henri Verbeet wrote: > This imlicitly gets rid of the "auto" option as well, since there's no way > to explicitly specify it. This will no doubt cause its share of > regressions, but I prefer actually fixing those bugs to running into the > surface implementation switching code every time I try to fix something in > ddraw. This will break 2D-only apps in situations where OpenGL is not available. It would be a good idea to use SURFACE_GDI automatically in those situations. (I'm not sure if ddraw without GL works at all right now, we have no systems that run the tests with this setup) It will make it impossible to run some apps out of the box(e.g. the ones currently affected by bug 2082, and old QuickTime versions). That's fine with me, it's not like those apps are working at the moment, and I guess the switching breaks more than it fixes.

2 3

Re: [3/7] dinput: Added enumerated devices to ConfigureDevices dialog
by Alexandre Julliard 01 Sep '11

01 Sep '11

Lucas Fialho Zawacki <lfzawacki(a)gmail.com> writes: > +static INT_PTR CALLBACK ConfigureDevicesDlgProc(HWND dialog, UINT uMsg, WPARAM wParam, LPARAM lParam) > +{ > + static LPDIACTIONFORMATW lpdiaf; > + static DIDevicesData devices_data; > + static ConfigureDevicesData *conf_data; > + > + switch(uMsg) > + { > + case WM_INITDIALOG: > + /* Initialize action format and enumerate devices */ > + conf_data = (ConfigureDevicesData*) lParam; > + lpdiaf = conf_data->params->lprgFormats; It doesn't make sense to pass the info as WM_INITDIALG parameter if it's going to be stored in global variables anyway. A better way would be to store this in the window info. -- Alexandre Julliard julliard(a)winehq.org

4 3

WineHQ Maintenance.
by Jeremy Newman 01 Sep '11

01 Sep '11

We will be performing upgrades and maintenance to the WineHQ.org server starting at 1800 CDT on Wednesday August 31st. This process will take the server off-line for about an hour. The Websites (www,appdb,forums), and Mailing lists, and Git will be off-line during this period. -Newman

1 1

Re: fake patch #2 just to test error emails
by buildbot＠kegel.com 31 Aug '11

31 Aug '11

The Buildbot has detected a failed build on builder runtests while building Wine. Full details are available at: http://buildbot.kegel.com/builders/runtests/builds/166 BUILD FAILED: failed git For more info about this message, see http://wiki.winehq.org/BuildBot

1 0

Re: cmd/tests: Add README doc file
by Alexandre Julliard 31 Aug '11

31 Aug '11

Frédéric Delanoy <frederic.delanoy(a)gmail.com> writes: > --- > programs/cmd/tests/README | 120 +++++++++++++++++++++++++++++++++++++++++++++ > 1 files changed, 120 insertions(+), 0 deletions(-) > create mode 100644 programs/cmd/tests/README That sort of thing should be on the wiki. READMEs in the source are never maintained properly. -- Alexandre Julliard julliard(a)winehq.org

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel August 2011