warning: variable ‘_qzz_res’ set but not used [-Wunused-but-set-variable]
That's valgrind stuff. Apparently I might need a valgrind update or
something, I'm not 100% sure what's going on.
A few more can be fixed with FIXME()s instead of comments.
J. Leclanche
== 32-bit ==
ccach
On 11/4/2011 20:21, Jacek Caban wrote:
On 11/04/11 17:11, Nikolay Sivov wrote:
On 11/4/2011 20:00, Jacek Caban wrote:
Hi Nikolay,
On 11/04/11 16:46, Nikolay Sivov wrote:
+if(This->data->vtbl&& This->data->vtbl->invoke) {
+hres = This->data->vtbl->invoke(This->outer, id, lcid,
wF
On 11/04/11 17:11, Nikolay Sivov wrote:
On 11/4/2011 20:00, Jacek Caban wrote:
Hi Nikolay,
On 11/04/11 16:46, Nikolay Sivov wrote:
+if(This->data->vtbl&& This->data->vtbl->invoke) {
+hres = This->data->vtbl->invoke(This->outer, id, lcid,
wFlags, pdp, pvarRes, pei);
+if (
On 11/4/2011 20:00, Jacek Caban wrote:
Hi Nikolay,
On 11/04/11 16:46, Nikolay Sivov wrote:
+if(This->data->vtbl&& This->data->vtbl->invoke) {
+hres = This->data->vtbl->invoke(This->outer, id, lcid,
wFlags, pdp, pvarRes, pei);
+if (hres != E_NOTIMPL) return hres;
+}
I'm curious why you've chosen to work on this. Is there a program
relying on this, or do you have some .NET debugging tools you'd like
to use? Or are you thinking we'd implement our own debugging tool as
well (perhaps extending winedbg)?
Better debugging tools for wine/mono would definitely be nic
Hi Nikolay,
On 11/04/11 16:46, Nikolay Sivov wrote:
+if(This->data->vtbl&& This->data->vtbl->invoke) {
+hres = This->data->vtbl->invoke(This->outer, id, lcid, wFlags, pdp,
pvarRes, pei);
+if (hres != E_NOTIMPL) return hres;
+}
Using E_NOTIMPL for special meaning here
Christian Inci writes:
> @@ -149,6 +149,12 @@ BOOL WINAPI GetUserProfileDirectoryW( HANDLE hToken,
> LPWSTR lpProfileDir,
>
> TRACE( "%p %p %p\n", hToken, lpProfileDir, lpcchSize );
>
> +if (!hToken)
> +{
> +SetLastError( ERROR_INVALID_HANDLE );
> +return FALSE;
On Thu, Nov 3, 2011 at 10:05 PM, Hin-Tak Leung wrote:
> I just had a rather odd incident earlier today when I just launched "wine
> cmd", and saw that my process monitor max-out to 100% - and it continued,
> until I finished what I intended to do and exited cmd, minutes later. I
> wasn't doing an
I just had a rather odd incident earlier today when I just launched "wine cmd",
and saw that my process monitor max-out to 100% - and it continued, until I
finished what I intended to do and exited cmd, minutes later. I wasn't doing
anything else and no typing anything in the cmd console either
