Quote from: samidare1234 on 15 October, 2015, 10:48:24 PMwavpack.mmphttps://mega.nz/#!qo4wkCSDIt says "Enter decryption key"
So... the base address of wavpack.exe is 0x400000. The fault offset is 0x00007ff8c9c2ed90, so the fault address is 0x7FF8CA02ED90 (correct me if I'm wrong). But there's nothing at this addredd. The only thing above 0x80000000 is ntdll.dll, but it starts at 0x7FF8CC140000.Don't know what it means. On my computer, there's nothing above 0x80000000 because wavpack doesn't have LargeAddressAware flag.I took the official wavpack.exe and set this flag in its header. Maybe this will prevent it from crashing?
And of course in the 64-bit version all pointers are going to be 64-bits wide, so the flag should be obsolete now
Probably this setting was copied from settings for 32-bit exe files into the settigs for 64-bit project?
And of course in the 64-bit version all pointers are going to be 64-bits wide, so the flag should be obsolete now (unless someone ported code that stores pointers in hard-coded 32-bit integers, which is very poor design).
The price of paranoia is eternal vigilance.
When I open wavpack.sln in MSVS 2013, the following linker options are not default (Release,x64):Enable Incremental Linking: No (/INCREMENTAL:NO)Generate Debug Info: NoSubSystem: Console (/SUBSYSTEM:CONSOLE)Enable Large Addresses: No (/LARGEADDRESSAWARE:NO)References: Yes (/OPT:REF)Enable COMDAT Folding: Yes (/OPT:ICF)Randomized Base Address: No (/DYNAMICBASE:NO)Target Machine: MachineX64 (/MACHINE:X64)
I could replicate the crash samidare1234 reported on English Windows 10 by installing EMET and marked wavpack.exe to get protected by all the default mitigations.I tested the behavior on some other random x64 programs where protecting them with EMET alone showed no issues but once largeaddressaware bit was altered they instantly crashed. So I too agree that changing the header bit is all you need to do.
Quote from: lvqcl on 17 October, 2015, 06:21:05 PMWhen I open wavpack.sln in MSVS 2013, the following linker options are not default (Release,x64):Thanks, most of these make sense. I either changed them to allow the programs to link (/INCREMENTAL) or are obvious (/SUBSYSTEM:CONSOLE, although probably the library and DLL do not need this).However, I don't understand MachineX64. Obviously that must be set the way it is to generate x64 code, right?
When I open wavpack.sln in MSVS 2013, the following linker options are not default (Release,x64):
By "not default" I meant that these options have some defined values (denoted as bold font), not just <inherit from parent or project defaults>.
Hi, had the same problem with the DirectShow Filter (CoreWavPack 1.2.0) and Windows 10. Change to 32bit solved the problem.