(Windows) Crashes after debug

[Spidy123222]

Currently on a properly setup windows install of jitstreamer it currently crashes when you activate jit. everything else like mounting or pairing works perfectly fine.

Error 1

Fault bucket 1807719142595307350, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: jit_streamer-x86_64-pc-windows-gnu.exe
P2: 0.0.0.0
P3: 6245fc3d
P4: ntdll.dll
P5: 10.0.19041.1566
P6: 1be73aa8
P7: c0000005
P8: 00000000000a6c3b
P9:
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER91CE.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER929A.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER92BA.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER92C8.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9317.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_jit_streamer-x86_4a539bd47932fac9f1456fb992a3601e9027a61d_f2fb59df_f6a88e12-0cf4-430f-88a7-489fd1b3a29c

Analysis symbol:
Rechecking for solution: 0
Report Id: d0cb5db3-0a61-45cb-abff-604a32cc0128
Report Status: 268435456
Hashed bucket: 321e6364b225864319164efb84112756
Cab Guid: 0

Error 2

Faulting application name: jit_streamer-x86_64-pc-windows-gnu.exe, version: 0.0.0.0, time stamp: 0x6245fc3d
Faulting module name: ntdll.dll, version: 10.0.19041.1566, time stamp: 0x1be73aa8
Exception code: 0xc0000005
Fault offset: 0x00000000000a6c3b
Faulting process id: 0x3134
Faulting application start time: 0x01d84a16b1e9a51c
Faulting application path: C:\Users\NameUnimportant\Downloads\jitstreamer\jit_streamer-x86_64-pc-windows-gnu.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d0cb5db3-0a61-45cb-abff-604a32cc0128
Faulting package full name:
Faulting package-relative application ID:

[jkcoxson]

Can you give us information about the system? OS, architecture, iPhone model etc.

[Spidy123222]

OS: windows 10 21h2 build 19044.1620
Architecture: intel x86_64
Cpu: i3 350m (specified incase if instruction set extension is not included likely not a limit though)
Ram: 16gb
idevice: iPhone 8 Plus iOS 15.0.2
The logs was received from event viewer in the original post.

[jkcoxson]

The build system has changed many times since the opening of this issue, does it still occur?

[Spidy123222]

I haven't been able to test it. There are no pre-made binaries to test that with i could try out building at some point.

[jkcoxson]

If anyone wants to help debug this, it needs to be run in an mingw64 env so we can see the unwind or possibly a segfault. Running in an MSVC env doesn't seem to give proper crash information.

[Redd12345]

ok so @jkcoxson, i used msys2 mingw64 to run the program with logging enabled and here is a screenshot of the logs. Hope this helps.