November 2010 - Wine-Devel - list.winehq.org

Re: cmd: Fix Italian translation
by Matteo Bruni Nov. 21, 2010

Nov. 21, 2010

> -L'etichetta che è l'obiettivo di un GOTO può essere lunga fino a 255 caratteri\n\ > +L'etichetta che è la destinazione di un GOTO può essere lunga fino a 255 caratteri\n\ I believe this sentence as a whole sounds quite awkward. Maybe something like "Un'etichetta che sia destinazione di un GOTO..." or simply "L'etichetta di destinazione di un GOTO..." would be better.

2 1

Re: [comctl32/tests 2/2] Get rid of some commented out lines
by Marvin Nov. 20, 2010

Nov. 20, 2010

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=7197 Your paranoid android. === W7PRO (32 bit propsheet) === propsheet.c:524: Test failed: The Add button has not been pressed! propsheet.c:681: Test failed: property sheet with custom window proc: the msg 0x001c was expected, but got msg 0x0047 instead === W7PROX64 (32 bit propsheet) === propsheet.c:524: Test failed: The Add button has not been pressed! propsheet.c:681: Test failed: property sheet with custom window proc: the msg 0x001c was expected, but got msg 0x0047 instead

1 0

building a winelib dll?
by Seth Burleigh Nov. 20, 2010

Nov. 20, 2010

Im trying to build a simple winelib. Its not working and is returning 'error 127'. I have some question: (1) how do i determine which functions are exported by wine? All i see using nm zmq.dll.so is the names of my proxy function (add_proxy) instead of the name that is going to be called by the windows program (add) (2) whats the point of a spec file? what im saying is that i can build my files without a spec file and no error message is produced. In what stage of building is the spec file actually used? (3) is there any way to debug just specifically the errors produced by my stub dll under wine? somehow specify a debug channel where the real reason for 'error 127' is? The stub dll being dynamically loaded by a program for which i have no source code. I am using these simple test files: //in zmq.c #include "zmq.h" #include "wine/debug.h" #include <windef.h> long WINAPI add_proxy(long a,long b) { return a+b; } ;;in zmq.dll.spec @ stdcall add( long long ) add_proxy and then i do winegcc -c -o zmq.o zmq.c winegcc -shared -o zmq.dll.so zmq.o However, i notice that i can just get rid of the spec file and no error messages are produced which makes no sense since the dll is supposed to redirect calls to add to add_proxy. And once i use the windows program to call function add, i get the 'error 127', which means it cant find the function 'add.'

1 2

Group Picture Wineconf 2010
by Marcus Meissner Nov. 20, 2010

Nov. 20, 2010

Hi, The group picture taken this morning: http://www.flickr.com/photos/marcusmeissner/5191522943/ For all the ones who staid at home ;) Ciao, Marcus

2 1

Patch for bug 25063 - _pclose should wait for the command processor to terminate and return it's exit status
by Borut Razem Nov. 20, 2010

Nov. 20, 2010

On 11/18/2010 02:54 PM, Alexandre Julliard wrote > Yes, you need to grow it dynamically. That doesn't mean you need a linear search. Here is the new patch: dynamically allocated array of process handles indexed by fd, no linear search. The patch compiles without errors but I haven't done any tests yet. Please review it and let me know if you are satisfied with the approach. In case of the positive answer I'll do some testing ant let you know about results. P.S.: MSVCRT_MAX_FILES is (re)defined in process.c and should be same as MSVCRT_MAX_FILES in file.c. It would be better to define it only once in a header file, for example in msvcrt.h. Do you agree? Borut --- dlls/msvcrt/process.c | 101 ++++++++++++++++++++++++++++++++++++++++++++++++- 1 files changed, 99 insertions(+), 2 deletions(-)

1 0

RE: [dlls/dbgeng]: add initial stub dll implementation
by Volodymyr Shcherbyna Nov. 19, 2010

Nov. 19, 2010

Hello Alexandre, I assume you were checking my patch (id: 68619) ( http://source.winehq.org/patches/data/68619) and marked it as "Apply Failure". If so, can you please double check? For the sake of the test, I setup wine-git on another machine to see if this patch works, and it seems to be OK. The following commands: patch -p1 < 0001-Implementing-stub-version-of-dbgeng.dll-Debugger-Eng.txt git add dlls/dbgeng/Makefile.in ./tools/make_makefiles autoconf ./configure make properly integrate and build dbgeng in wine tree. I was following exact guidelines from http://wiki.winehq.org/Developers-Hints , and I it seems like the patch is OK, or I am missing something not documented on the wiki :) Well, I am a newbie in wine/linux, so, of course I can be wrong ... P.S. I attach patch to this email just in case (the same patch I sent to wine patch list). Thanks, -- avec meilleures salutations, Volodymyr

2 2

Re: [2/3] msxml3: Validate node content in xmlnode_put_dataType() (resend)
by Jacek Caban Nov. 19, 2010

Nov. 19, 2010

On 11/19/10 6:22 AM, Adam Martinson wrote: > --- > dlls/msxml3/msxml_private.h | 1 + > dlls/msxml3/node.c | 113 > ++++++++++++++++++++++++++----------------- > dlls/msxml3/schema.c | 94 +++++++++++++++++++++++++++++++++-- > 3 files changed, 158 insertions(+), 50 deletions(-) > @@ -887,71 +891,92 @@ static HRESULT WINAPI xmlnode_put_dataType( { xmlnode *This = impl_from_IXMLDOMNode( iface ); HRESULT hr = E_FAIL; + xmlChar *str; + XDR_DT dt; TRACE("(%p)->(%s)\n", This, debugstr_w(dataTypeName)); if(dataTypeName == NULL) return E_INVALIDARG; + if (This->node->type != XML_ELEMENT_NODE) + return E_FAIL; Again, this should go to element object then. Jacek

1 0

Re: [PATCH 2/3] ws2_32: fix up iovecs after transmission in WS2_send instead of WS2_sendto
by Marvin Nov. 19, 2010

Nov. 19, 2010

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=7173 Your paranoid android. === WXPPROSP3 (32 bit sock) === sock.c:3404: Test failed: Expected event sequence [FD_READ(0)], got [] sock.c:3411: Test failed: Expected event sequence [], got [FD_READ(0)] === WVISTAADM (32 bit sock) === sock.c:862: Test failed: gethostbyname() failed unexpectedly: 11004

1 0

Re: [PATCH 2/3] ws2_32: fix up iovecs after transmission in WS2_send instead of WS2_sendto
by Marvin Nov. 18, 2010

Nov. 18, 2010

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=7171 Your paranoid android. === W98SE (32 bit sock) === sock.c:2661: Test failed: Failed to start overlapped send 0 - 0 - 1048576/1048576

1 0

Re: [PATCH 1/3] ws2_32/tests: add a test for an overlapped send
by Marvin Nov. 18, 2010

Nov. 18, 2010

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=7170 Your paranoid android. === W98SE (32 bit sock) === sock.c:2661: Test failed: Failed to start overlapped send 0 - 0 - 1048576/1048576

1 0