Re: fork error when trying to call VirtualAlloc with size==0

On Wed, 21 May 2025, Jeremy Drake via Cygwin wrote: > the child to not be very fruitful, but maybe there's some debugging to be > done there Well, found the bug that results in a 0 size. size is a DWORD, but mb.RegionSize is 0x2. mb.RegionSize is SIZE_T, but I figure size_t is appropria

Re: fork error when trying to call VirtualAlloc with size==0

On Tue, 20 May 2025, Yuyi Wang wrote: > Thank you for your reply. The DLL is a "proc macro" DLL for rustc, which means > that it's not designed to be changed after created. However, I've also found > that this stage-1 compiler doesn't always trigger this failure: it just > trigger > fork failure

Create a sales pipeline

Hello, I hope you're doing well! If reaching high-quality, targeted leads is part of your strategy, we'd love to help. Our B2B data solutions offer customized insights and verified contacts, ensuring you connect with decision-makers relevant to your business. To provide a sample, could you sha

EBADF from write() if foreign pty is opened via /proc/PID/fd/N symlink

Unexpected behavior of an uncommon use case: $ uname -r 3.7.0-0.98.gb39b510c1ce6.x86_64 $ cygstart mintty - # Start second terminal In second terminal: $ echo $$; tty 1219 /dev/pty1 Back to first terminal: $ dd of=/proc/1219/fd/1 <<<"Hello" # errno=EBADF dd: error writing '/proc/1219/fd/1':