Getting GVIM error when running gf2 under WSL2 on Windows 11
ShreyasJejurkar opened this issue · comments
Hi there,
I am learning FASM, and for debugging FASM, I use GF2. So far my experience is good and it works like a charm under WSL2 on Windows 11.
I am currently facing an issue where I can not give input to my assembly code when I debug that using gf2 and run the gf2 from the command line, I get the below error.
Following are GVIM version details.
The application shows red when there is a write or read sys call. And just stuck there. I guess this is related to gvim error somehow.
The GVIM error can be ignored, it is only for the optional integration features.
The red traffic light is displayed when the target is running; the green traffic light is displayed when you can enter commands.
So here, in the above screenshot red is showing, and the currently executing instruction is syscall which is write, so does that mean, it's executing write sys call? But why's it taking that much time? If I debug the same in gdb CMD, I instantly see the text on the console which is by syscall.
Is there any way we can see logs of it, so that we can get more clarity.
@nakst ??