Post B6YcVKCOPD9gSdkbGC by hugo@chaos.social
 (DIR) More posts by hugo@chaos.social
 (DIR) Post #B6YbvoL6rljpW0tT8K by q3k@social.hackerspace.pl
       1 likes, 1 repeats
       
       when you search for a proof of concept demonstrating something cursed that oughta just work and the first result is your own github gist from 4 years ago(in this case, executing Linux syscalls from an .exe running under Wine https://gist.github.com/q3k/e5952111283ea59ee78a7699919a055b )
       
 (DIR) Post #B6Ybvoc7qVLiMmr3ei by wolf480pl@mstdn.io
       0 likes, 0 repeats
       
       @q3k does it, like, show a windows CLI window for the first printf?
       
 (DIR) Post #B6YcVKCOPD9gSdkbGC by hugo@chaos.social
       0 likes, 0 repeats
       
       @wolf480pl @q3k why should it? `printf` just writes to stdout.
       
 (DIR) Post #B6YcfnzmTfHllkqhqS by wolf480pl@mstdn.io
       0 likes, 0 repeats
       
       @hugo @q3k so, I'm not very familiar with win32, but I thought win32 programs are either windowed or console programs, and if they're windowed then their output goes nowhere, while if they're console programs then they spawn a console window when started without one...
       
 (DIR) Post #B6Yi7pawckIOboPnpg by domi@donotsta.re
       0 likes, 0 repeats
       
       @wolf480pl @hugo @q3k the console window is traditionally implemented by a background conhost.exe process, which (AFAIR) wine forgoes completely and binds to stdio. see wine cmd for a demo
       
 (DIR) Post #B6Yi9O8xesY0374KBM by artemist@mildlyfunctional.gay
       1 likes, 0 repeats
       
       @q3k does that still work? i thought wine was using syscall user dispatch now(not that kernel support was ever technically required for that, they could have implemented it with kvm instead)
       
 (DIR) Post #B6Zd8fBSVowjzq228u by alina@girldick.gay
       0 likes, 0 repeats
       
       @q3k wtf lmao that's amazing