August 2013 - Wine-Devel - list.winehq.org

Re: comsvcs: Add dll comsvcs (resend)
by André Hentschel Aug. 16, 2013

Aug. 16, 2013

Am 16.08.2013 12:39, schrieb Alistair Leslie-Hughes: > Hi, > > > Changelog: > comsvcs: Add dll comsvcs > > > Best Regards > Alistair Leslie-Hughes you missed the configure.ac part?

1 0

Re: [3/3] ntdll/tests: Add a bunch of overlapped IO tests for files.
by Marvin Aug. 16, 2013

Aug. 16, 2013

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=26708 Your paranoid android. === WXPX64 (64 bit file) === file.c:1791: Test failed: expected STATUS_SUCCESS, got 0 file.c:1817: Test failed: expected STATUS_SUCCESS, got 0 file.c:1844: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:1855: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:1874: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:1894: Test failed: expected STATUS_SUCCESS, got 0 file.c:1927: Test failed: expected STATUS_SUCCESS, got 0 file.c:1008: Test failed: Invalid ioSb.Information: 3 === WVISTAX64 (64 bit file) === file.c:1791: Test failed: expected STATUS_SUCCESS, got 0 file.c:1817: Test failed: expected STATUS_SUCCESS, got 0 file.c:1844: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:1855: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:1874: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:1884: Test failed: expected STATUS_SUCCESS, got 0 file.c:1894: Test failed: expected STATUS_SUCCESS, got 0 file.c:1903: Test failed: expected STATUS_SUCCESS, got 0 file.c:1927: Test failed: expected STATUS_SUCCESS, got 0 file.c:2030: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:2037: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:2088: Test failed: expected STATUS_SUCCESS, got 0 file.c:2095: Test failed: expected STATUS_SUCCESS, got 0 file.c:2104: Test failed: expected STATUS_SUCCESS, got 0 file.c:2110: Test failed: expected STATUS_SUCCESS, got 0 file.c:1008: Test failed: Invalid ioSb.Information: 3 === W7PROX64 (64 bit file) === file.c:1791: Test failed: expected STATUS_SUCCESS, got 0 file.c:1817: Test failed: expected STATUS_SUCCESS, got 0 file.c:1844: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:1855: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:1874: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:2030: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:2037: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:2088: Test failed: expected STATUS_SUCCESS, got 0 file.c:2095: Test failed: expected STATUS_SUCCESS, got 0 file.c:2104: Test failed: expected STATUS_SUCCESS, got 0 file.c:2110: Test failed: expected STATUS_SUCCESS, got 0 file.c:1008: Test failed: Invalid ioSb.Information: 3 === TEST64_W7SP1 (64 bit file) === file.c:1791: Test failed: expected STATUS_SUCCESS, got 0 file.c:1817: Test failed: expected STATUS_SUCCESS, got 0 file.c:1844: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:1855: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:1874: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:1884: Test failed: expected STATUS_SUCCESS, got 0 file.c:1894: Test failed: expected STATUS_SUCCESS, got 0 file.c:1903: Test failed: expected STATUS_SUCCESS, got 0 file.c:1927: Test failed: expected STATUS_SUCCESS, got 0 file.c:2030: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:2037: Test failed: expected STATUS_END_OF_FILE, got 0xc0000011 file.c:2088: Test failed: expected STATUS_SUCCESS, got 0 file.c:2095: Test failed: expected STATUS_SUCCESS, got 0 file.c:2104: Test failed: expected STATUS_SUCCESS, got 0 file.c:2110: Test failed: expected STATUS_SUCCESS, got 0 file.c:1008: Test failed: Invalid ioSb.Information: 3

2 1

Re: [2/3] ntdll/tests: Use official path for temporary files instead of current directory.
by Marvin Aug. 16, 2013

Aug. 16, 2013

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=26707 Your paranoid android. === WXPX64 (64 bit file) === file.c:1008: Test failed: Invalid ioSb.Information: 3 === WVISTAX64 (64 bit file) === file.c:1008: Test failed: Invalid ioSb.Information: 3 === W7PROX64 (64 bit file) === file.c:1008: Test failed: Invalid ioSb.Information: 3 === TEST64_W7SP1 (64 bit file) === file.c:1008: Test failed: Invalid ioSb.Information: 3

1 0

Re: [3/3] ntdll: Implement compatible typelib section
by Marvin Aug. 16, 2013

Aug. 16, 2013

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=26698 Your paranoid android. === W2KPROSP4 (32 bit actctx) === Timeout === WXPPROSP2 (32 bit actctx) === actctx.c:1375: Test failed: got 409, 1043 === WXPX64 (32 bit actctx) === actctx.c:1375: Test failed: got 409, 1043 === W2K3R2SESP2 (32 bit actctx) === actctx.c:1375: Test failed: got 409, 1043 === WVISTAX64 (32 bit actctx) === actctx.c:1375: Test failed: got 409, 1043 === W7PROX64 (32 bit actctx) === actctx.c:1375: Test failed: got 409, 1043 === TEST64_W7SP1 (32 bit actctx) === actctx.c:1375: Test failed: got 409, 1043 === WXPX64 (64 bit actctx) === actctx.c:1375: Test failed: got 409, 1043 === WVISTAX64 (64 bit actctx) === actctx.c:1375: Test failed: got 409, 1043 === W7PROX64 (64 bit actctx) === actctx.c:1375: Test failed: got 409, 1043 === TEST64_W7SP1 (64 bit actctx) === actctx.c:1375: Test failed: got 409, 1043

1 0

Re: [2/3] ntdll: Added support for all typelib section attributes
by Marvin Aug. 16, 2013

Aug. 16, 2013

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=26697 Your paranoid android. === W2KPROSP4 (32 bit actctx) === Timeout === WXPPROSP2 (32 bit actctx) === actctx.c:1357: Test failed: got 409 === WXPX64 (32 bit actctx) === actctx.c:1357: Test failed: got 409 === W2K3R2SESP2 (32 bit actctx) === actctx.c:1357: Test failed: got 409 === WVISTAX64 (32 bit actctx) === actctx.c:1357: Test failed: got 409 === W2K8SE (32 bit actctx) === actctx.c:1357: Test failed: got 409 === W7PROX64 (32 bit actctx) === actctx.c:1357: Test failed: got 409 === TEST64_W7SP1 (32 bit actctx) === actctx.c:1357: Test failed: got 409 === WXPX64 (64 bit actctx) === actctx.c:1357: Test failed: got 409 === WVISTAX64 (64 bit actctx) === actctx.c:1357: Test failed: got 409 === W7PROX64 (64 bit actctx) === actctx.c:1357: Test failed: got 409 === TEST64_W7SP1 (64 bit actctx) === actctx.c:1357: Test failed: got 409

1 0

Re: [1/3] kernel32: Some tests for typelib sections
by Marvin Aug. 16, 2013

Aug. 16, 2013

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=26696 Your paranoid android. === W2KPROSP4 (32 bit actctx) === Timeout

1 0

Re: mscoree: Redirect .NET 1.0 to .NET 2.0
by Alexandre Julliard Aug. 15, 2013

Aug. 15, 2013

Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> writes: > Hi, > > > Changelog: > mscoree: Redirect .NET 1.0 to .NET 2.0 It doesn't work: ../../../tools/runtest -q -P wine -M mscoree.dll -T ../../.. -p mscoree_test.exe.so mscoree.c && touch mscoree.ok mscoree.c:179: Test failed: version is L"v1.1.4322" , expected L"v2.0.50727" mscoree.c:187: Test failed: GetRequestedRuntimeInfo returned 80131700 mscoree.c:188: Test failed: version is L"" , expected L"v2.0.50727" make: *** [mscoree.ok] Error 3 -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: configure.ac: allow disabling winemac.drv (try 2)
by Alexandre Julliard Aug. 15, 2013

Aug. 15, 2013

Austin English <austinenglish(a)gmail.com> writes: > try 2: don't unconditionally disable ApplicationServices.h > > Tested on 10.7 > diff --git a/configure.ac b/configure.ac > index 0e3df61..5e1fe10 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -70,6 +70,7 @@ AC_ARG_WITH(pthread, AS_HELP_STRING([--without-pthread],[do not use the pthrea > AC_ARG_WITH(sane, AS_HELP_STRING([--without-sane],[do not use SANE (scanner support)])) > AC_ARG_WITH(tiff, AS_HELP_STRING([--without-tiff],[do not use TIFF])) > AC_ARG_WITH(v4l, AS_HELP_STRING([--without-v4l],[do not use v4l1 (v4l support)])) > +AC_ARG_WITH(winemac, AS_HELP_STRING([--without-winemac],[do not build native Mac (Cocoa) driver])) It should be --disable-winemac.drv, and it should work fine already, same as with any other dll. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: mscoree: Attempt to load the assembly from the application directory
by Vincent Povirk Aug. 15, 2013

Aug. 15, 2013

This seems suspicious to me. You appear to be taking the namespace of the class and assuming it's an assembly name. Is there really no other information in the registry that could be used to identify the assembly?

3 4

Re: msvcrt: add support for _chsize_s
by Ken Sharp Aug. 14, 2013

Aug. 14, 2013

On 14/08/13 20:08, morphiend wrote: > -@ stub _chsize_s > +@ cdecl _chsize_s(long int64) msvcrt._chsize > +#@ stub _chsize_s Oops..

1 0

Re: mscoree: Redirect .NET 1.0 to .NET 2.0
by Vincent Povirk Aug. 14, 2013

Aug. 14, 2013

Looks good, thanks.

1 0

Possibility of adding a new patch status
by Hugh McMaster Aug. 14, 2013

Aug. 14, 2013

Hi everyone, Wine patches currently have a status described in http://source.winehq.org/patches, yet for patches with the status of 'New', the status becomes confusing. The legend describes 'New' status as "Patch not even looked at yet, there's still hope...". This is ideal for new patches submitted within that 24-hour commit cycle. But I'm finding it difficult to follow patches that remain with a status of 'New' for longer than the 24-hour patch cycle. Obviously, on the weekend, patches are held over till Monday, so a longer lead-time is expected. During weekdays, however, it is unclear what is happening with some patches. This, ultimately, raises the question of timeliness. Has the patch been looked at? If it has, the status often describes what action was taken - committed, rejected, superseded, etc. This is fine, but some patches remain with a status of 'New'. Experience has told me that patches remaining with a status of 'New' are incorrect in some way. But this is not always the case. If the patch is incorrect, but close to being accepted, the patch's status should reflect this, by changing to something like "Revision needed". Of course, the "Rejected" status is also appropriate, depending on the severity of coding error. Also, there are likely to be many times when the maintainer has not had time to evaluate some patches. This means the patch is not new (i.e. recently submitted), but is awaiting review. Once again, I believe the patch status should reflect this situation. The status could be "Not yet reviewed". In summary, the 'New' status should be reserved for patches that are actually new. Just some thoughts.

3 7

Re: gdiplus: Only clip strings if rectangle width and height are positive.
by Dmitry Timoshkov Aug. 14, 2013

Aug. 14, 2013

Vincent Povirk <madewokherd(a)gmail.com> wrote: > if (!(format_flags & StringFormatFlagsNoClip) && > - scaled_rect.Width != 1 << 23 && scaled_rect.Height != 1 << 23) > + scaled_rect.Width != 1 << 23 && scaled_rect.Height != 1 << 23 && > + rect->Width > 0.0 && rect->Height > 0.0) > { > /* FIXME: If only the width or only the height is 0, we should probably still clip */ > rgn = CreatePolygonRgn(corners, 4, ALTERNATE); Probably FIXME should be removed then. -- Dmitry.

2 1

wine-bugs change?
by Thomas Spear Aug. 13, 2013

Aug. 13, 2013

Hi all, I've been subscribed to the lists for several years now, archiving all of the conversations in case a situation ever arises where a backup copy is needed. I've had a filter setup in gmail for wine-bugs that has worked perfectly fine for a long time now, but over the last couple of days, I've noticed that all emails sent to or from wine-bugs are now being directed to my inbox in addition to the folder I have the filter setup for. I'm planning on contacting Google as well, but thought I should cover all of the bases by asking here if there have been any changes made to that list specifically that might have caused the filter to not work. I've tried editing the filter so that I can see what messages it searches for, and it appears to be working properly, in that it appears to locate the emails I have the filter setup for, including those that are currently in both my inbox and the folder I specified to have them moved to, so it could be that there is an issue with the "Skip Inbox" setting of the filter, specifically. But again, I thought I would ask (because Google will and I'll need to have an answer for them) what changes, if any, have been made recently on the mailman side of things. Thank you, Thomas

4 6

Wine Gecko repo
by Jacek Caban Aug. 13, 2013

Aug. 13, 2013

Hi, A few months ago, SourceForge did some deep changes in their Git (and not only) repo hosting. While doing it, the location of repos has changed (which is extremely stupid, if you ask me). The problem is that while doing the update, they also switched to their own Web interface for git. And this shiny new interface doesn't work at all for Wine Gecko repo (wine-gecko.git probably too big and complicated). See [1], it claims to be analyzing the repo, but it has been like that since the switch was done. I contacted them [2] and they are aware of the problem, but it's still not fixed. I already got some questions about outdated sources. Also, our Wiki points to this Git in a few places. I never updated those links because I was waiting for the new repo to work. I think it's time to move the repo. The question is, where should it go? - Github seems to be the choice for most project currently and it's already used by Wine Mono. - Reconsider source.winehq.org. This was not chosen due to account management overhead, but that's the only way to avoid problems similar to recent Sourceforge one (Github nor anyone else is going to give us any guarantees) - Other ideas? I'd appreciate opinions. Thanks, Jacek [1] https://sourceforge.net/p/wine/wine-gecko/ci/master/tree/ [2] https://sourceforge.net/p/forge/site-support/4299/

3 2

Process for reporting security bugs?
by achurch+wine-devel＠achurch.org Aug. 13, 2013

Aug. 13, 2013

[Please cc: me on any replies since I'm not subscribed to the list.] Hi, Is there a specific process for reporting security-related bugs in Wine? I've looked through winehq.org but haven't found any mention of such; I just wanted to make sure I haven't overlooked anything before posting the bug in a publicly visible manner. Thanks, --Andrew Church achurch+wine-devel(a)achurch.org http://achurch.org/

3 5

Re: [1/2] cmd: Add handler support for Ctrl-C and Ctrl-Break events
by Hugh McMaster Aug. 13, 2013

Aug. 13, 2013

On Monday, 12 August 2013, Ruslan Kabatsayev wrote: >I've tried applying your both patches, and it appears that Ctrl+C at >cmd prompt still closes cmd, although pressing it while "dir /s /w" is running works as expected. Hi Ruslan, I've just tested the Ctrl-C patches on the most recent version of Wine available from the Git repository. After patching, compiling and installing, I found no problems with either of the patches as you described. Ctrl-C did nothing when cmd.exe was open and no command was running. To be clear, I was running cmd.exe via wineconsole in Linux Mint 14: 1. wineconsole cmd.exe 2. Press Ctrl-C --> cmd.exe remains open. But if you run cmd.exe via wine itself, the terminal will terminate cmd.exe when Ctrl-C is pressed. 1. wine cmd.exe 2. Press Ctrl-C --> returned to terminal prompt. I hope this helps. If the patch still doesn't seem to work correctly, please let me know what operating system you use, and I'll run further tests. Hugh

2 2

Re: Compiler warnings on Debian Sid kfreebsd-i386
by Ken Sharp Aug. 12, 2013

Aug. 12, 2013

On 12/08/13 20:15, Mislav Blazevic wrote: > It seems that xmlBufPtr was renamed to xmlBufferPtr in new libxml. It does seem that way. :-) Or maybe :-(

1 0

Re: Compiler warnings on Debian Sid kfreebsd-i386
by Mislav Blazevic Aug. 12, 2013

Aug. 12, 2013

It seems that xmlBufPtr was renamed to xmlBufferPtr in new libxml. On Mon, Aug 12, 2013 at 9:15 PM, Mislav Blazevic <krofnica996(a)gmail.com>wrote: > It seems that xmlBufPtr was renamed to xmlBufferPtr in new libxml. > > > > On Mon, Aug 12, 2013 at 9:11 PM, Ken Sharp <kennybobs(a)o2.co.uk> wrote: > >> Following my previous e-mail (http://www.winehq.org/** >> pipermail/wine-devel/2013-**August/100754.html<http://www.winehq.org/pipermail/wine-devel/2013-August/100754.html>) >> I have since moved from Wheezy to Sid to work around a Debian bug. >> >> libxml2 has been updated (2.8.0+dfsg1-7+nmu1 --> 2.9.1+dfsg1-3) as a >> result and introduced some new compiler warnings: >> >> /home/ken/wine-git/dlls/**msxml3/node.c: In function >> ‘htmldtd_dumpcontent’: >> /home/ken/wine-git/dlls/**msxml3/node.c:908:9: warning: passing argument >> 1 of ‘xmlBufferWriteQuotedString’ from incompatible pointer type [enabled >> by default] >> xmlBufferWriteQuotedString(**buf->buffer, cur->ExternalID); >> ^ >> In file included from /usr/include/libxml2/libxml/**parser.h:16:0, >> from /home/ken/wine-git/dlls/**msxml3/node.c:28: >> /usr/include/libxml2/libxml/**tree.h:1123:3: note: expected >> ‘xmlBufferPtr’ but argument is of type ‘xmlBufPtr’ >> xmlBufferWriteQuotedString(**xmlBufferPtr buf, >> ^ >> /home/ken/wine-git/dlls/**msxml3/node.c:912:13: warning: passing >> argument 1 of ‘xmlBufferWriteQuotedString’ from incompatible pointer type >> [enabled by default] >> xmlBufferWriteQuotedString(**buf->buffer, cur->SystemID); >> ^ >> In file included from /usr/include/libxml2/libxml/**parser.h:16:0, >> from /home/ken/wine-git/dlls/**msxml3/node.c:28: >> /usr/include/libxml2/libxml/**tree.h:1123:3: note: expected >> ‘xmlBufferPtr’ but argument is of type ‘xmlBufPtr’ >> xmlBufferWriteQuotedString(**xmlBufferPtr buf, >> ^ >> /home/ken/wine-git/dlls/**msxml3/node.c:918:9: warning: passing argument >> 1 of ‘xmlBufferWriteQuotedString’ from incompatible pointer type [enabled >> by default] >> xmlBufferWriteQuotedString(**buf->buffer, cur->SystemID); >> ^ >> In file included from /usr/include/libxml2/libxml/**parser.h:16:0, >> from /home/ken/wine-git/dlls/**msxml3/node.c:28: >> /usr/include/libxml2/libxml/**tree.h:1123:3: note: expected >> ‘xmlBufferPtr’ but argument is of type ‘xmlBufPtr’ >> xmlBufferWriteQuotedString(**xmlBufferPtr buf, >> ^ >> /home/ken/wine-git/dlls/**msxml3/node.c: In function >> ‘node_transform_node’: >> /home/ken/wine-git/dlls/**msxml3/node.c:974:21: warning: passing >> argument 1 of ‘xmlBufferContent’ from incompatible pointer type [enabled by >> default] >> content = xmlBufferContent(output->**buffer); >> ^ >> In file included from /usr/include/libxml2/libxml/**parser.h:16:0, >> from /home/ken/wine-git/dlls/**msxml3/node.c:28: >> /usr/include/libxml2/libxml/**tree.h:734:3: note: expected >> ‘xmlBufferPtr’ but argument is of type ‘xmlBufPtr’ >> xmlBufferContent (const xmlBufferPtr buf); >> ^ >> >> Hopefully these mean something to someone. >> >> >> >

1 0

Compiler warnings on Debian Sid kfreebsd-i386
by Ken Sharp Aug. 12, 2013

Aug. 12, 2013

Following my previous e-mail (http://www.winehq.org/pipermail/wine-devel/2013-August/100754.html) I have since moved from Wheezy to Sid to work around a Debian bug. libxml2 has been updated (2.8.0+dfsg1-7+nmu1 --> 2.9.1+dfsg1-3) as a result and introduced some new compiler warnings: /home/ken/wine-git/dlls/msxml3/node.c: In function ‘htmldtd_dumpcontent’: /home/ken/wine-git/dlls/msxml3/node.c:908:9: warning: passing argument 1 of ‘xmlBufferWriteQuotedString’ from incompatible pointer type [enabled by default] xmlBufferWriteQuotedString(buf->buffer, cur->ExternalID); ^ In file included from /usr/include/libxml2/libxml/parser.h:16:0, from /home/ken/wine-git/dlls/msxml3/node.c:28: /usr/include/libxml2/libxml/tree.h:1123:3: note: expected ‘xmlBufferPtr’ but argument is of type ‘xmlBufPtr’ xmlBufferWriteQuotedString(xmlBufferPtr buf, ^ /home/ken/wine-git/dlls/msxml3/node.c:912:13: warning: passing argument 1 of ‘xmlBufferWriteQuotedString’ from incompatible pointer type [enabled by default] xmlBufferWriteQuotedString(buf->buffer, cur->SystemID); ^ In file included from /usr/include/libxml2/libxml/parser.h:16:0, from /home/ken/wine-git/dlls/msxml3/node.c:28: /usr/include/libxml2/libxml/tree.h:1123:3: note: expected ‘xmlBufferPtr’ but argument is of type ‘xmlBufPtr’ xmlBufferWriteQuotedString(xmlBufferPtr buf, ^ /home/ken/wine-git/dlls/msxml3/node.c:918:9: warning: passing argument 1 of ‘xmlBufferWriteQuotedString’ from incompatible pointer type [enabled by default] xmlBufferWriteQuotedString(buf->buffer, cur->SystemID); ^ In file included from /usr/include/libxml2/libxml/parser.h:16:0, from /home/ken/wine-git/dlls/msxml3/node.c:28: /usr/include/libxml2/libxml/tree.h:1123:3: note: expected ‘xmlBufferPtr’ but argument is of type ‘xmlBufPtr’ xmlBufferWriteQuotedString(xmlBufferPtr buf, ^ /home/ken/wine-git/dlls/msxml3/node.c: In function ‘node_transform_node’: /home/ken/wine-git/dlls/msxml3/node.c:974:21: warning: passing argument 1 of ‘xmlBufferContent’ from incompatible pointer type [enabled by default] content = xmlBufferContent(output->buffer); ^ In file included from /usr/include/libxml2/libxml/parser.h:16:0, from /home/ken/wine-git/dlls/msxml3/node.c:28: /usr/include/libxml2/libxml/tree.h:734:3: note: expected ‘xmlBufferPtr’ but argument is of type ‘xmlBufPtr’ xmlBufferContent (const xmlBufferPtr buf); ^ Hopefully these mean something to someone.

1 0

Question about implementing application compatibility
by Mislav Blazevic Aug. 12, 2013

Aug. 12, 2013

For past two weeks I've been implementing apphelp.dll. I got that one working and moved onto kernel32 part of magic. According to various papers and blogs it seems that windows logs all exes and dlls ever executed in registry[1] and uses it as cache to lookup if binary needs to be shimmed or patched (if file isn't found, hard lookup of shim database is done) It is loaded on boot and saved back to registry on shutdown. This is awfully overcomplicated (plus I do not know how to make such a "global" variable in wine) so I was wondering is it OK to implement this differently than windows does it. It would be simpler to control app compat with environmental variable. It would mean that Base*Appcompat* kernel32 APIs would remain unimplemented but as far as I know, no application uses them anyway, other than windows internally. What do you think? [1] https://github.com/mandiant/ShimCacheParser

2 1

Re: ntdll/tests: test FileDispositionInformation file class
by Marvin Aug. 12, 2013

Aug. 12, 2013

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=26661 Your paranoid android. === WXPX64 (32 bit file) === file.c:1318: Test failed: Unexpected NtQueryInformationFile result (expected STATUS_INVALID_INFO_CLASS, got c0000002) === WVISTAX64 (32 bit file) === file.c:1318: Test failed: Unexpected NtQueryInformationFile result (expected STATUS_INVALID_INFO_CLASS, got c0000002) === W7PROX64 (32 bit file) === file.c:1318: Test failed: Unexpected NtQueryInformationFile result (expected STATUS_INVALID_INFO_CLASS, got c0000002) === TEST64_W7SP1 (32 bit file) === file.c:1318: Test failed: Unexpected NtQueryInformationFile result (expected STATUS_INVALID_INFO_CLASS, got c0000002)

1 0

Re: [1/2] cmd: Add handler support for Ctrl-C and Ctrl-Break events
by Ruslan Kabatsayev Aug. 11, 2013

Aug. 11, 2013

Hi, On Sun, Aug 11, 2013 at 12:33 PM, Hugh McMaster <hugh.mcmaster(a)masterindexing.com> wrote: > Jason Edmeades and I have developed a patch that handles Ctrl-C and Ctrl-Break events in wineconsole's cmd.exe. > > The patch supports interactive mode, batch contexts and both the cmd /c and cmd /k modes, meaning that pressing Ctrl-C no longer closes cmd.exe. I've tried applying your both patches, and it appears that Ctrl+C at cmd prompt still closes cmd, although pressing it while "dir /s /w" is running works as expected. > > For loops, commands such as 'dir /s /w' and other such commands can be stopped. Batch scripts prompt the user whether the current batch execution should end. > > --- > programs/cmd/builtins.c | 95 ++++++++++++++++++++++++++++++++++++++++++----- > programs/cmd/cmd.rc | 2 + > programs/cmd/wcmd.h | 7 ++++ > programs/cmd/wcmdmain.c | 65 +++++++++++++++++++++++++++++++- > 4 files changed, 158 insertions(+), 11 deletions(-) > > > Regards, Ruslan

1 0

Compiler warnings on Debian kfreebsd-i386
by Ken Sharp Aug. 11, 2013

Aug. 11, 2013

Some interesting, some not: /home/ken/wine-git/dlls/iphlpapi/ipstats.c:1898:24: warning: ‘get_pid_map’ defined but not used [-Wunused-function] /home/ken/wine-git/dlls/iphlpapi/ipstats.c:1953:21: warning: ‘find_owning_pid’ defined but not used [-Wunused-function] /home/ken/wine-git/dlls/jscript/parser.y: conflicts: 1 shift/reduce, 18 reduce/reduce /home/ken/wine-git/dlls/msi/sql.y: conflicts: 1 reduce/reduce /home/ken/wine-git/dlls/ntdll/directory.c: In function ‘wine_getdirentries’: /home/ken/wine-git/dlls/ntdll/directory.c:1710:5: warning: passing argument 4 of ‘getdirentries’ from incompatible pointer type [enabled by default] In file included from /home/ken/wine-git/dlls/ntdll/directory.c:29:0: /usr/include/dirent.h:313:18: note: expected ‘__off_t * __restrict__’ but argument is of type ‘long int *’ /home/ken/wine-git/dlls/vbscript/parser.y: conflicts: 6 shift/reduce /home/ken/wine-git/programs/winedbg/dbg.y: conflicts: 1 shift/reduce, 1 reduce/reduce /home/ken/wine-git/programs/winedbg/dbg.y: conflicts: 1 shift/reduce, 1 reduce/reduce

2 5

Is it a little bug in wbemprox?
by Jing Li Aug. 10, 2013

Aug. 10, 2013

Hi, When I ran a simple win32 program just via WMI with query of "SELECT * from Win32_Directory", wine1.6 crashed. And when I checked the related code I found that the function of "static UINT seed_dirs( struct dirstack *dirstack, const struct expr *cond, WCHAR root, UINT *count )", in dlls/wbemprox/builtin.c:1086, accessing cond's member without checking if it's NULL! Unfortunately a NULL is passed to it. That's why my program crashed. It's a bug, right?

2 1