Crash on Windows 7 x64
Dear @TomWright, Windows 7 users like me are unable to use your app on anymore, because @golang team betrayed the community and cut off such users in their recent compiler. Could you be so kind to do something about that? Examples of apps such as Brename, Croc and Nexttrace (to name a few) convince that this is possible.
$ dasel.exe
Exception 0xc0000005 0x8 0x0 0x0
PC=0x0
runtime.asmstdcall(0x22fcf8)
/opt/hostedtoolcache/go/1.22.0/x64/src/runtime/sys_windows_amd64.s:75 +0x7a fp=0x22fc80 sp=0x22fc60 pc=0x46f4fa
rax 0x0
rbx 0xd609f8
rcx 0xde5aa8
rdx 0x20
rdi 0x7fffffdd000
rsi 0x22fe78
rbp 0x22fdc0
rsp 0x22fc58
r8 0x0
r9 0x22fee8
r10 0x3ca2e8
r11 0xc000004000
r12 0x22fec8
r13 0x0
r14 0xd5f640
r15 0x3
rip 0x0
rflags 0x10293
cs 0x33
fs 0x53
gs 0x2b
I dealt with this briefly yesterday and gave some quick workaround options here: https://github.com/TomWright/dasel/issues/390
I plan on adding clear instructions/workarounds for windows 7 users, and potentially adding a new build step for windows 7 that will compile against go 1.20, with the caveat that this may become unavailable at a point that I start using newer languages features.
The pre-built EXE for Dasel v2.6.0 seems to work on Win7 if you use VxKex. I did a quick test and everything seems to be working fine.
https://github.com/vxiiduu/VxKex/releases/tag/Version1.0.0.999
@vxiiduu, thank you for a workaround, but I don't understand why @TomWright hesitates to set up another compiling pipeline for Windows 7 just as @schollz did about Croc to keep this app accessible to a wider audience.
@sergeevabc it's not about hesitation... It's about the fact that I maintain this in my spare time and have an incredibly busy life at the moment.
This is an open source project. If you need this fixed now, please go ahead and raise a pull request. I'm always accepting contributions.