http://bugs.winehq.org/show_bug.cgi?id=26760
Summary: SIV generates fixme:rpc:handle_bind_error unexpected status value 1765 Product: Wine Version: 1.3.17 Platform: x86 URL: http://rh-software.com/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: rpc AssignedTo: wine-bugs@winehq.org ReportedBy: ray@pobox.co.uk
When I run SIV on exiting I sometimes get fixme:rpc:handle_bind_error unexpected status value 1765.
I expect this is because an entry needs to be added for RPC_S_NO_CONTEXT_AVAILABLE to the switch in handle_bind_error() but I can not figure out what reject_reason should be set to.
A typical run log when I start SIV and just press [ OK ] is:
ray@RUW:~/siv$ wine siv32x fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub fixme:netapi32:NetGetJoinInformation Stub (null) 0x22981cc 0x22981d0 fixme:ntoskrnl:KeInitializeMutex stub: 0x111320, 0 fixme:ntoskrnl:HalGetBusData (4 0 0 0x1119ec 256) stub! fixme:ntdll:NtQuerySystemInformation (0x00000051,0x229805c,0x00000024,0x2298084) stub fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_CACHE_INFORMATION fixme:rpc:handle_bind_error unexpected status value 1765 ray@RUW:~/siv$
http://bugs.winehq.org/show_bug.cgi?id=26760
ray@pobox.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Difficulty|--- |Minutes
http://bugs.winehq.org/show_bug.cgi?id=26760
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Component|rpc |-unknown Resolution| |INVALID
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2011-04-13 04:52:00 CDT --- FIXME is not a bug. If there is no problem in an application there is nothing to fix.
http://bugs.winehq.org/show_bug.cgi?id=26760
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED Difficulty|Minutes |---
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2011-04-13 04:52:58 CDT --- Closing.
Also please don't touch the 'Difficulty' field in future, it's not supposed to be filled by a reporter.
http://bugs.winehq.org/show_bug.cgi?id=26760
--- Comment #3 from ray@pobox.co.uk 2011-04-13 07:51:34 CDT --- (In reply to comment #1)
FIXME is not a bug. If there is no problem in an application there is nothing to fix.
Looking at the code to me it is clear that Wine should be fixed. I am at a total loss as to why you have no interist in fixing wine.
http://bugs.winehq.org/show_bug.cgi?id=26760
--- Comment #4 from Dmitry Timoshkov dmitry@codeweavers.com 2011-04-13 08:11:26 CDT --- (In reply to comment #3)
Looking at the code to me it is clear that Wine should be fixed. I am at a total loss as to why you have no interist in fixing wine.
In the console output you've attached there are many other fixme messages, what's the point in treating them differently?
Feel free to send patches.
http://bugs.winehq.org/show_bug.cgi?id=26760
--- Comment #5 from ray@pobox.co.uk 2011-04-13 08:26:07 CDT --- (In reply to comment #4)
(In reply to comment #3)
Looking at the code to me it is clear that Wine should be fixed. I am at a total loss as to why you have no interist in fixing wine.
In the console output you've attached there are many other fixme messages, what's the point in treating them differently?
Feel free to send patches.
It's allready on it way !
If you check you will find bug reports for several of the other ones.
http://bugs.winehq.org/show_bug.cgi?id=26760
--- Comment #6 from ray@pobox.co.uk 2011-04-16 14:20:33 CDT --- I have found what generates this and sometimes it generates other errors. It's when I stop my SIVDriver service. If I do this while SIV is running SIV restarts it and I typically get the following.
To reproduce this from SIV do Menu->Windows->Services->WIN32 Control, then press [SIVDriver] and then [Stop]. You may need to do the stop a few times.
Every time the driver starts you get fixme:ntoskrnl:HalGetBusData...
Should I change the status from Closed?
fixme:rpc:handle_bind_error unexpected status value 1765 err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {f27407ee-83c1-4334-bda5-7072b94b29c7}, guard (nil) err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {07c226d3-5669-4bae-bd0e-d37ec63bcf4d}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {f27407ee-83c1-4334-bda5-7072b94b29c7}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {f27407ee-83c1-4334-bda5-7072b94b29c7}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a fixme:ntoskrnl:HalGetBusData (4 0 0 0x1119c8 256) stub! fixme:rpc:handle_bind_error unexpected status value 1765 fixme:ntoskrnl:HalGetBusData (4 0 0 0x1119d0 256) stub! fixme:rpc:handle_bind_error unexpected status value 1765 err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {e218cb77-91b1-4ebb-9261-a248da4c0fa2}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {e218cb77-91b1-4ebb-9261-a248da4c0fa2}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {12329d46-4a42-4b02-91bd-1e38896501e7}, guard (nil) err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {676d856a-6f4e-40e7-ad49-c33d42aaa256}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {676d856a-6f4e-40e7-ad49-c33d42aaa256}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {e612a8e6-e94c-4afa-9321-38cad13de288}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {9b67eb70-7b7c-4e67-8f5e-30a5752c634b}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {9b67eb70-7b7c-4e67-8f5e-30a5752c634b}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {ab1a4617-64d5-4d89-9e44-3d420e3d20c3}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {1b006977-84ab-4e3e-afb8-1ce42363d3d0}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {1b006977-84ab-4e3e-afb8-1ce42363d3d0}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {cd0ff6da-f07f-4d51-b999-19b2284a6172}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {d46e9c92-b98b-4cf4-a18a-f916c7d4d8e3}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {d46e9c92-b98b-4cf4-a18a-f916c7d4d8e3}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a err:rpc:RpcServerAssoc_FindContextHandle no context handle found for uuid {4df869ec-aeac-482c-b023-4ce296280fd1}, guard (nil) err:rpc:I_RpcReceive we got fault packet with status 0x1c00001a fixme:ntoskrnl:HalGetBusData (4 0 0 0x1119c8 256) stub! fixme:rpc:handle_bind_error unexpected status value 1765 ray@RUW:~/siv$
http://bugs.winehq.org/show_bug.cgi?id=26760
ray@pobox.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ray@pobox.co.uk
http://bugs.winehq.org/show_bug.cgi?id=26760
--- Comment #7 from ray@pobox.co.uk 2011-04-16 14:24:00 CDT --- Created an attachment (id=34153) --> (http://bugs.winehq.org/attachment.cgi?id=34153) Patch to stop the report
http://bugs.winehq.org/show_bug.cgi?id=26760
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|ray@rh-software.com |
--- Comment #8 from Dmitry Timoshkov dmitry@codeweavers.com 2011-04-16 23:53:26 CDT --- If there is no problem with an application then there is nothing to fix.
There is no need to add your e-mail to the cc: list if you are the reporter.
http://bugs.winehq.org/show_bug.cgi?id=26760
--- Comment #9 from ray@rh-software.com 2011-04-17 01:33:11 CDT --- (In reply to comment #8)
If there is no problem with an application then there is nothing to fix.
What you say is contrabicts what Alexandre Julliard said. Which is correct? When I asked:
I have assumed that FIXME messages should not be displayed and if they are they should be fixed. Is my assumption correct?
Yes, but for FIXMEs that don't cause any trouble except the message, that's extremely low priority. IOW, if you want it fixed you'll most likely have to do it yourself.
-- Alexandre Julliard julliard@winehq.org
http://bugs.winehq.org/show_bug.cgi?id=26760
--- Comment #10 from Dmitry Timoshkov dmitry@codeweavers.com 2011-04-17 03:25:48 CDT --- What kind of a bug your patch does fix? In which way? What is the source of the problem? Where is it? Do you have a test case showing that your patch is the right way to fix the problem?
Once you can answer the questions above you may probably create a proper fix.
http://bugs.winehq.org/show_bug.cgi?id=26760
ray@rh-software.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |ABANDONED
--- Comment #11 from ray@rh-software.com 2011-04-17 03:47:42 CDT --- OK. I give up.
-
wine-bugs＠winehq.org