[Bug 47987] New: Output with WINEDEBUG=warn+all contains a class of false positive 'file not found' messages.
https://bugs.winehq.org/show_bug.cgi?id=47987 Bug ID: 47987 Summary: Output with WINEDEBUG=warn+all contains a class of false positive 'file not found' messages. Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mail(a)marekpasnikowski.name Distribution: --- How to Reproduce: Run winecfg with a WINEDEBUG=warn+all flag. Witness pages of the following kind of messages, which are mostly blatantly incorrect:
wine winecfg 0009:warn:ntdll:FILE_CreateFile L"\\??\\Z:\\usr\\bin\\..\\lib\\wine\\kernel32.dll" not found (c0000034)
I can run a complex game within this very prefix - it is healthy. I have been witnessing this problem for years. And now it is actively hindering my efforts to locate the reason for a game crash, because of its verbose nature. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #1 from Zebediah Figura <z.figura12(a)gmail.com> --- Well... yes. That's what the WARN channel is for, messages that might signal an error but don't necessarily. That's why it's off by default. But debugging naturally means sifting through things that *might* be responsible for failure in order to find something that actually *is*. It could be that failure to create a different file is exactly what's tripping up this program later. We can't magically filter out the relevant failures from the irrelevant failures. If it's too much of a problem, you might try WINEDEBUG=warn+all,warn-ntdll, or otherwise just preprocessing logs to filter out anything containing "warn:ntdll:FILE_CreateFile". -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 --- Comment #2 from Marek Paśnikowski <mail(a)marekpasnikowski.name> --- Misunderstanding. The bug is about messages "file not found" for files which exist. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Alexandre Julliard <julliard(a)winehq.org> --- If you really have a /usr/lib/wine/kernel32.dll file, you are doing something wrong (and then you wouldn't see the message). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 Marek Paśnikowski <mail(a)marekpasnikowski.name> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED --- Comment #4 from Marek Paśnikowski <mail(a)marekpasnikowski.name> --- I did pick a line at random, just to show the general form of it. However, what about those: 000b:warn:ntdll:FILE_CreateFile L"\\??\\C:\\windows" not found (c0000035) 000b:warn:ntdll:FILE_CreateFile L"\\??\\C:\\windows\\system32" not found (c0000035) 000b:warn:ntdll:FILE_CreateFile L"\\??\\C:\\windows\\syswow64" not found (c0000035) I double checked just now and they definitely exist. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID --- Comment #5 from Alexandre Julliard <julliard(a)winehq.org> --- Yes, that's why these have a different error code. We could print something else than "not found" in that case, but it's not worth a lot of effort. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 Marek Paśnikowski <mail(a)marekpasnikowski.name> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED --- Comment #6 from Marek Paśnikowski <mail(a)marekpasnikowski.name> --- I am confused by this conversation now. My current understanding is that you will not fix this bug because it's not worth the effort, right? However, it does not change the fact that the problem exists. I am interested in getting it fixed - if it is within my ability, I am ready to do something myself. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID --- Comment #7 from Alexandre Julliard <julliard(a)winehq.org> --- There is nothing to fix, failure to open a file should be a warning, it doesn't matter why it failed to open. If you absolutely want, you can change "not found" to "failed to open" or something like that. It makes no difference really. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 Marek Paśnikowski <mail(a)marekpasnikowski.name> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED --- Comment #8 from Marek Paśnikowski <mail(a)marekpasnikowski.name> --- I am getting agitated, so I am minimising my message to avoid emotional overflows. Following along - why are the files failing to be opened? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID --- Comment #9 from Alexandre Julliard <julliard(a)winehq.org> --- You can lookup the failure status code in include/ntstatus.h. For instance c0000034 is STATUS_OBJECT_NAME_NOT_FOUND. And please stop changing the resolution, nothing was fixed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 Marek Paśnikowski <mail(a)marekpasnikowski.name> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED --- Comment #10 from Marek Paśnikowski <mail(a)marekpasnikowski.name> --- I never changed resolution - I simply used the "Additional comment" tool. When I tried to reply with email - it was rejected. There is a serious communication problem here. I am going to sit back and leave this bug for now, but I am not satisfied. Something IS wrong and I am told it ISN'T. As things are, in order to confirm validity of those warnings I would have to go through dozens to thousands of files. This is not feasible. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID --- Comment #11 from Alexandre Julliard <julliard(a)winehq.org> --- That's how Wine debugging works I'm afraid. It's always about finding the needle in the haystack. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 --- Comment #12 from Zebediah Figura <z.figura12(a)gmail.com> --- To clarify at least one thing, paths like "\??\C:\windows\" really are going to be nonexistent. The operative difference is the global \??\ prefix. That means, roughly, "look in the device namespace, not the file system". -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47987 André H. <nerv(a)dawncrow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv(a)dawncrow.de Status|RESOLVED |CLOSED --- Comment #13 from André H. <nerv(a)dawncrow.de> --- closing invalid -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla