Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On windows backtrace might return false positives. #6654

Open
Ekopalypse opened this issue Oct 19, 2020 · 6 comments
Open

On windows backtrace might return false positives. #6654

Ekopalypse opened this issue Oct 19, 2020 · 6 comments
Labels
Bug This tag is applied to issues which reports bugs. Status: Confirmed This bug has been confirmed to be valid by a contributor.

Comments

@Ekopalypse
Copy link
Contributor

Ekopalypse commented Oct 19, 2020

V version:
OS:
OS: windows, Microsoft Windows 7 Professional v7601 64-bit
Processor: 4 cpus, 64bit, little endian, Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz
CC version: N/A

vroot: D:\ProgramData\Compiler\v
vexe: D:\ProgramData\Compiler\v\v.exe
vexe mtime: 2020-10-19 20:16:19
is vroot writable: true
V full version: V 0.1.29 230e986.3ae3196

Git version: git version 2.19.1.windows.1
Git vroot status: 0.1.29-657-g3ae3196d
.git/config present: true
thirdparty/tcc: N/A

What did you do?
On Windows compile the example at https://gist.github.com/Ekopalypse/f49c99661871f9794398b4ebd007014c
with -cc msvc. Execute it and open a context menu by right click on one of the files or folders.
Multiple exceptions are generated.

What did you expect to see?
The context menu for that item

What did you see instead?
In addition to displaying the context menu a bunch of exceptions are reported.

@Ekopalypse Ekopalypse added the Bug This tag is applied to issues which reports bugs. label Oct 19, 2020
@danieldaeschle
Copy link
Member

Exception is not from V. The exception is expected and should be whitelisted somehow. If anyone knows how this works or what V needs he can implement it or give the solution to this problem.

@danieldaeschle
Copy link
Member

@Ekopalypse
Copy link
Contributor Author

Perhaps some additional error checking, as described at https://docs.microsoft.com/en-us/windows/win32/learnwin32/error-handling-in-com, are helpful.

@Ekopalypse
Copy link
Contributor Author

Jfi - linked gist has been updated to make the test work with newer windows versions as well.

@ArtemkaKun
Copy link
Contributor

Hi @Ekopalypse,

does this problem still exist for fresh V (0.2.4)?

@Ekopalypse
Copy link
Contributor Author

Yes it does

D:\scripts\v\tests\bug\6654>v version
V 0.2.4 799c95d

D:\scripts\v\tests\bug\6654>v -cc msvc run issue.v
Unhandled Exception 0x6BA
23: RaiseException             ?? : address = 0xb603e70
22: RpcRaiseException          ?? : address = 0xb603e90
21: NdrClientCall3             ?? : address = 0xb603ea0
20: Ndr64AsyncClientCall       ?? : address = 0xb603eb0
19: NdrClientCall3             ?? : address = 0xb603ec0
18: NPGetCaps                  ?? : address = 0xb603ed0
17: NPOpenEnum                 ?? : address = 0xb603ee0
16: WNetOpenEnumW              ?? : address = 0xb603e80
15: WNetOpenEnumW              ?? : address = 0x1360de00
14: WriteCabinetState          ?? : address = 0x1360de10
13: WriteCabinetState          ?? : address = 0x1360de20
12: Ordinal733                 ?? : address = 0x1360de30
11: Ordinal893                 ?? : address = 0x1360de40
10: SHCreateShellFolderView    ?? : address = 0x1360de50
9 : SHPathPrepareForWriteW     ?? : address = 0x1360de60
8 : SHPathPrepareForWriteW     ?? : address = 0x1360de70
7 : StgMakeUniqueName          ?? : address = 0x1360de80
6 : StgMakeUniqueName          ?? : address = 0x1360de90
5 : StgMakeUniqueName          ?? : address = 0x1360dea0
4 : Ordinal733                 ?? : address = 0x1360deb0
3 : StgMakeUniqueName          ?? : address = 0x1370f0f0
2 : SHRegGetUSValueW           ?? : address = 0x1370f100
1 : BaseThreadInitThunk        ?? : address = 0x1370f110
0 : RtlUserThreadStart         ?? : address = 0x1370f120
GetOpenFileNameW error: 0

@ArtemkaKun ArtemkaKun added the Status: Confirmed This bug has been confirmed to be valid by a contributor. label Feb 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug This tag is applied to issues which reports bugs. Status: Confirmed This bug has been confirmed to be valid by a contributor.
Projects
None yet
Development

No branches or pull requests

3 participants